raeez.com

raeez.com may not be SSL secured

Free website and domain report on raeez.com

Last Updated: 30th April, 2020 Update Now
Overview

Snoop Summary for raeez.com

This is a free and comprehensive report about raeez.com. Raeez.com is hosted in Toronto, Ontario in Canada on a server with an IP address of 159.203.57.78, where CAD is the local currency and the local language is English. If raeez.com was to be sold it would possibly be worth $362 USD (based on the daily revenue potential of the website over a 24 month period). Raeez.com receives an estimated 169 unique visitors every day - a decent amount of traffic! This report was last updated 30th April, 2020.

About raeez.com

Site Preview: raeez.com raeez.com
Title: 50,000+ Free eBooks in the Genres you Love | raeez.com
Description: Great selection of modern and classic books waiting to be discovered. All free and available in most ereader formats.
Keywords and Tags: blogs, wiki
Related Terms: chegg ereader, ereader
Fav Icon:
Age: Over 15 years old
Domain Created: 29th July, 2009
Domain Updated: 28th May, 2019
Domain Expires: 29th July, 2020
Review

Snoop Score

1/5

Valuation

$362 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 6,986,637
Alexa Reach: <0.0001%
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 169
Monthly Visitors: 5,149
Yearly Visitors: 61,747
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $15 USD
Yearly Revenue: $176 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: raeez.com 9
Domain Name: raeez 5
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 84
Performance 99
Accessibility 97
Best Practices 85
SEO 100
Progressive Web App 38
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for raeez.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.7 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.7 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.7 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
First CPU Idle — 0.7 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive raeez.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://raeez.com/
0
109.10500003956
3534
15596
200
text/html
Document
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
131.11399998888
234.7979999613
23748
23499
200
text/css
Stylesheet
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
131.24300003983
377.14699981734
327499
327248
200
text/css
Stylesheet
http://raeez.com/template/_many/logo.png
131.34199986234
200.49199997447
3182
2934
200
image/png
Image
http://raeez.com/genre-1.png
135.7419998385
268.28800002113
5263
19641
404
text/html
Image
http://raeez.com/genre-2.png
136.21299993247
232.67999989912
5263
19640
404
text/html
Image
http://raeez.com/genre-3.png
136.32099982351
246.4499999769
5263
19640
404
text/html
Image
http://raeez.com/genre-4.png
136.43499999307
215.95799992792
5264
19640
404
text/html
Image
http://raeez.com/genre-5.png
136.59699982964
238.71499998495
5262
19641
404
text/html
Image
http://raeez.com/genre-6.png
136.68300001882
210.20099986345
5264
19641
404
text/html
Image
http://raeez.com/genre-7.png
136.97399990633
214.64699995704
5265
19641
404
text/html
Image
http://raeez.com/genre-8.png
137.40599993616
250.35699992441
5262
19640
404
text/html
Image
http://raeez.com/genre-9.png
137.55599991418
178.36399981752
5263
19640
404
text/html
Image
http://raeez.com/genre-10.png
137.65699998476
234.90699985996
5266
19659
404
text/html
Image
http://raeez.com/genre-11.png
137.79599987902
219.75199994631
5265
19658
404
text/html
Image
http://raeez.com/genre-12.png
137.96900003217
211.01600001566
5265
19659
404
text/html
Image
http://raeez.com/template/_many/bookdisplaysmall.jpg
146.56100003049
363.5419998318
224750
224497
200
image/jpeg
Image
http://raeez.com/template/_many/bookcoverssmall2.jpg
147.20999985002
365.10899988934
221752
221499
200
image/jpeg
Image
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
415.39799980819
460.31599980779
5302
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
415.78199993819
456.53099985793
5263
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
418.9559998922
460.70399996825
5292
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
419.83699984848
557.88600002415
5277
19713
404
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
144.031
8.29
158.601
12.059
409.53
22.579
432.177
42.895
493.177
91.987
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Raeez.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Raeez.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Raeez.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Raeez.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 61 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/bookcoverssmall2.jpg
221499
62795
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 110 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Raeez.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Raeez.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 868 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
http://raeez.com/template/_many/bookdisplaysmall.jpg
224750
http://raeez.com/template/_many/bookcoverssmall2.jpg
221752
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
5302
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
5292
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
5277
http://raeez.com/genre-10.png
5266
http://raeez.com/genre-11.png
5265
http://raeez.com/genre-12.png
5265
Avoids an excessive DOM size — 225 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
225
Maximum DOM Depth
20
Maximum Child Elements
12
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Raeez.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
229.048
7.659
1.151
Minimizes main-thread work — 0.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
100.665
Other
51.193
Rendering
39.609
Parse HTML & CSS
28.771
Script Evaluation
7.659
Script Parsing & Compilation
1.151
Keep request counts low and transfer sizes small — 22 requests • 868 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
22
888764
Image
16
518126
Stylesheet
2
351247
Font
3
15857
Document
1
3534
Media
0
0
Script
0
0
Other
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Opportunities

Eliminate render-blocking resources — Potential savings of 380 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Raeez.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
150
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
430
Remove unused CSS — Potential savings of 330 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Raeez.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
314086
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
23568
Enable text compression — Potential savings of 297 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327248
285434
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23499
18730

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Raeez.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
0
327499
http://raeez.com/template/_many/bookdisplaysmall.jpg
0
224750
http://raeez.com/template/_many/bookcoverssmall2.jpg
0
221752
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
0
23748
http://raeez.com/template/_many/logo.png
0
3182
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
44.917999999598
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
40.748999919742
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
41.748000076041
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of raeez.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Raeez.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Raeez.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Raeez.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that raeez.com should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 22 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://raeez.com/
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
http://raeez.com/template/_many/logo.png
http://raeez.com/genre-1.png
http://raeez.com/genre-2.png
http://raeez.com/genre-3.png
http://raeez.com/genre-4.png
http://raeez.com/genre-5.png
http://raeez.com/genre-6.png
http://raeez.com/genre-7.png
http://raeez.com/genre-8.png
http://raeez.com/genre-9.png
http://raeez.com/genre-10.png
http://raeez.com/genre-11.png
http://raeez.com/genre-12.png
http://raeez.com/template/_many/bookdisplaysmall.jpg
http://raeez.com/template/_many/bookcoverssmall2.jpg
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
http://raeez.com/genre-9.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-6.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-12.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-7.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-4.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-11.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-2.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-10.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-5.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-3.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-8.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-1.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Failed to load resource: the server responded with a status of 404 (Not Found)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for raeez.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of raeez.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
38

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of raeez.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of raeez.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 22 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://raeez.com/
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
http://raeez.com/template/_many/logo.png
http://raeez.com/genre-1.png
http://raeez.com/genre-2.png
http://raeez.com/genre-3.png
http://raeez.com/genre-4.png
http://raeez.com/genre-5.png
http://raeez.com/genre-6.png
http://raeez.com/genre-7.png
http://raeez.com/genre-8.png
http://raeez.com/genre-9.png
http://raeez.com/genre-10.png
http://raeez.com/genre-11.png
http://raeez.com/genre-12.png
http://raeez.com/template/_many/bookdisplaysmall.jpg
http://raeez.com/template/_many/bookcoverssmall2.jpg
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 82
Performance 87
Accessibility 97
Best Practices 85
SEO 100
Progressive Web App 41
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
87

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for raeez.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 3.2 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
First CPU Idle — 3.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 40 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive raeez.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://raeez.com/
0
39.70200009644
3534
15596
200
text/html
Document
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
51.917999982834
119.66699990444
23748
23499
200
text/css
Stylesheet
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
52.282999968156
227.96000004746
327499
327248
200
text/css
Stylesheet
http://raeez.com/template/_many/logo.png
52.554999943823
88.261000113562
3182
2934
200
image/png
Image
http://raeez.com/genre-1.png
52.712999982759
90.296000009403
5262
19640
404
text/html
Image
http://raeez.com/genre-2.png
54.959000088274
102.33699996024
5263
19641
404
text/html
Image
http://raeez.com/genre-3.png
55.270000128075
97.883000038564
5262
19640
404
text/html
Image
http://raeez.com/genre-4.png
55.417000083253
96.334000118077
5263
19640
404
text/html
Image
http://raeez.com/genre-5.png
55.523999966681
95.580999972299
5263
19641
404
text/html
Image
http://raeez.com/genre-6.png
55.61999999918
102.98199998215
5263
19640
404
text/html
Image
http://raeez.com/genre-7.png
56.010999949649
97.175000002608
5264
19640
404
text/html
Image
http://raeez.com/genre-8.png
56.119000073522
101.12600005232
5263
19641
404
text/html
Image
http://raeez.com/genre-9.png
56.463000131771
98.47000008449
5263
19640
404
text/html
Image
http://raeez.com/genre-10.png
56.540000019595
99.077000049874
5267
19659
404
text/html
Image
http://raeez.com/genre-11.png
56.639000074938
100.53599998355
5265
19658
404
text/html
Image
http://raeez.com/genre-12.png
56.730000069365
99.734999937937
5266
19658
404
text/html
Image
http://raeez.com/template/_many/bookdisplaysmall.jpg
62.89800000377
226.22700012289
224750
224497
200
image/jpeg
Image
http://raeez.com/template/_many/bookcoverssmall2.jpg
63.445999985561
224.60999991745
221752
221499
200
image/jpeg
Image
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
256.60500000231
301.14999995567
5303
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
257.00600002892
299.9060000293
5263
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
257.24299997091
299.29900006391
5292
0
404
text/html
Font
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
257.79299996793
300.37500010803
5276
19712
404
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
68.207
7.199
77.583
6.353
255.45
16.009
271.52
48.063
319.6
5.129
327.703
65.66
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Raeez.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Raeez.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Raeez.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Raeez.com should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 40 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Raeez.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Raeez.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 868 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
http://raeez.com/template/_many/bookdisplaysmall.jpg
224750
http://raeez.com/template/_many/bookcoverssmall2.jpg
221752
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
5303
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
5292
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
5276
http://raeez.com/genre-10.png
5267
http://raeez.com/genre-12.png
5266
http://raeez.com/genre-11.png
5265
Avoids an excessive DOM size — 225 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
225
Maximum DOM Depth
20
Maximum Child Elements
12
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Raeez.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
715.956
18.428
3.356
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
280.456
Rendering
198.8
Other
133.42
Parse HTML & CSS
81.496
Script Evaluation
18.428
Script Parsing & Compilation
3.356
Keep request counts low and transfer sizes small — 22 requests • 868 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
22
888763
Image
16
518124
Stylesheet
2
351247
Font
3
15858
Document
1
3534
Media
0
0
Script
0
0
Other
0
0
Third-party
0
0
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Metrics

First Contentful Paint — 3.2 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 3.2 s
The time taken for the primary content of the page to be rendered.

Opportunities

Serve images in next-gen formats — Potential savings of 61 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/bookcoverssmall2.jpg
221499
62795

Opportunities

Eliminate render-blocking resources — Potential savings of 2,010 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Raeez.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
780
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
2430
Remove unused CSS — Potential savings of 331 KB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Raeez.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327499
315057
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23748
23568
Enable text compression — Potential savings of 297 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
327248
285434
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
23499
18730

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Raeez.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
0
327499
http://raeez.com/template/_many/bookdisplaysmall.jpg
0
224750
http://raeez.com/template/_many/bookcoverssmall2.jpg
0
221752
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
0
23748
http://raeez.com/template/_many/logo.png
0
3182
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
44.544999953359
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
42.900000000373
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
42.056000092998

Other

First Contentful Paint (3G) — 6720 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of raeez.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Raeez.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Raeez.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Raeez.com may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that raeez.com should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 22 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://raeez.com/
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
http://raeez.com/template/_many/logo.png
http://raeez.com/genre-1.png
http://raeez.com/genre-2.png
http://raeez.com/genre-3.png
http://raeez.com/genre-4.png
http://raeez.com/genre-5.png
http://raeez.com/genre-6.png
http://raeez.com/genre-7.png
http://raeez.com/genre-8.png
http://raeez.com/genre-9.png
http://raeez.com/genre-10.png
http://raeez.com/genre-11.png
http://raeez.com/genre-12.png
http://raeez.com/template/_many/bookdisplaysmall.jpg
http://raeez.com/template/_many/bookcoverssmall2.jpg
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
URL Description
http://raeez.com/genre-1.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-5.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-4.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-7.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-3.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-9.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-10.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-12.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-11.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-8.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-2.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/genre-6.png
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Failed to load resource: the server responded with a status of 404 (Not Found)
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
Failed to load resource: the server responded with a status of 404 (Not Found)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for raeez.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of raeez.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
Legible text
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
41

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of raeez.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of raeez.com on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 22 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://raeez.com/
http://raeez.com/template/_many/css_3hv4mtqVMeGDyBz0Htb4e0KPszGCJnc7pORMrzuJl9Q.css
http://raeez.com/template/_many/css_y9k1vgDe6BTHHJzcAajgzuKkaMEgTGsd0Mlo5SHQxHo.css
http://raeez.com/template/_many/logo.png
http://raeez.com/genre-1.png
http://raeez.com/genre-2.png
http://raeez.com/genre-3.png
http://raeez.com/genre-4.png
http://raeez.com/genre-5.png
http://raeez.com/genre-6.png
http://raeez.com/genre-7.png
http://raeez.com/genre-8.png
http://raeez.com/genre-9.png
http://raeez.com/genre-10.png
http://raeez.com/genre-11.png
http://raeez.com/genre-12.png
http://raeez.com/template/_many/bookdisplaysmall.jpg
http://raeez.com/template/_many/bookcoverssmall2.jpg
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegularBold.ttf
http://raeez.com/themes/custom/mnybks/fonts/helvetica.ttf
http://raeez.com/themes/custom/mnybks/fonts/CenturyGothicRegular.ttf
http://raeez.com/themes/custom/mnybks/images/footer-logo.svg
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 159.203.57.78
Continent: North America
Country: Canada
Canada Flag
Region: Ontario
City: Toronto
Longitude: -79.3623
Latitude: 43.6547
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
DigitalOcean, LLC
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Google LLC 142.250.81.238
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
raeez.com. 159.203.57.78 IN 3599

NS Records

Host Nameserver Class TTL
raeez.com. ns-cloud-d1.googledomains.com. IN 21599
raeez.com. ns-cloud-d2.googledomains.com. IN 21599
raeez.com. ns-cloud-d3.googledomains.com. IN 21599
raeez.com. ns-cloud-d4.googledomains.com. IN 21599

MX Records

Priority Host Server Class TTL
1 raeez.com. aspmx.l.google.com. IN 3599
5 raeez.com. alt1.aspmx.l.google.com. IN 3599
5 raeez.com. alt2.aspmx.l.google.com. IN 3599
10 raeez.com. alt3.aspmx.l.google.com. IN 3599
10 raeez.com. alt4.aspmx.l.google.com. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
raeez.com. ns-cloud-d1.googledomains.com. cloud-dns-hostmaster.google.com. 21599

TXT Records

Host Value Class TTL
raeez.com. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.14.0 (Ubuntu)
Date: 30th April, 2020
Content-Type: text/html; charset=UTF-8
Connection: keep-alive

Whois Lookup

Created: 29th July, 2009
Changed: 28th May, 2019
Expires: 29th July, 2020
Registrar: Google LLC
Status: clientTransferProhibited
Nameservers: ns-cloud-d1.googledomains.com
ns-cloud-d2.googledomains.com
ns-cloud-d3.googledomains.com
ns-cloud-d4.googledomains.com
Owner Name: Contact Privacy Inc. Customer 1241259549
Owner Organization: Contact Privacy Inc. Customer 1241259549
Owner Street: 96 Mowat Ave
Owner Post Code: M4K 3K1
Owner City: Toronto
Owner State: ON
Owner Country: CA
Owner Phone: +1.4165385487
Owner Email: xwunuotkfrsz@contactprivacy.email
Admin Name: Contact Privacy Inc. Customer 1241259549
Admin Organization: Contact Privacy Inc. Customer 1241259549
Admin Street: 96 Mowat Ave
Admin Post Code: M4K 3K1
Admin City: Toronto
Admin State: ON
Admin Country: CA
Admin Phone: +1.4165385487
Admin Email: xwunuotkfrsz@contactprivacy.email
Tech Name: Contact Privacy Inc. Customer 1241259549
Tech Organization: Contact Privacy Inc. Customer 1241259549
Tech Street: 96 Mowat Ave
Tech Post Code: M4K 3K1
Tech City: Toronto
Tech State: ON
Tech Country: CA
Tech Phone: +1.4165385487
Tech Email: xwunuotkfrsz@contactprivacy.email
Full Whois: Domain Name: raeez.com
Registry Domain ID: 1563970888_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.google.com
Registrar URL: https://domains.google.com
Updated Date: 2019-05-28T06:21:23Z
Creation Date: 2009-07-29T20:25:05Z
Registrar Registration Expiration Date: 2020-07-29T20:25:05Z
Registrar: Google LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: registrar-abuse@google.com
Registrar Abuse Contact Phone: +1.8772376466
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Contact Privacy Inc. Customer 1241259549
Registrant Organization: Contact Privacy Inc. Customer 1241259549
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M4K 3K1
Registrant Country: CA
Registrant Phone: +1.4165385487
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: xwunuotkfrsz@contactprivacy.email
Registry Admin ID:
Admin Name: Contact Privacy Inc. Customer 1241259549
Admin Organization: Contact Privacy Inc. Customer 1241259549
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M4K 3K1
Admin Country: CA
Admin Phone: +1.4165385487
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: xwunuotkfrsz@contactprivacy.email
Registry Tech ID:
Tech Name: Contact Privacy Inc. Customer 1241259549
Tech Organization: Contact Privacy Inc. Customer 1241259549
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M4K 3K1
Tech Country: CA
Tech Phone: +1.4165385487
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: xwunuotkfrsz@contactprivacy.email
Name Server: NS-CLOUD-D1.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D2.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D3.GOOGLEDOMAINS.COM
Name Server: NS-CLOUD-D4.GOOGLEDOMAINS.COM
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-04-30T15:07:27Z <<<

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

Please register your domains at: https://domains.google.com/
This data is provided by Google for information purposes, and to assist
persons obtaining information about or related to domain name registration
records. Google does not guarantee its accuracy.
By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances, will you use this data to:
1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via E-mail (spam); or
2) enable high volume, automated, electronic processes that apply to this
WHOIS server.
These terms may be changed without prior notice.
By submitting this query, you agree to abide by this policy.

Nameservers

Name IP Address
ns-cloud-d1.googledomains.com 216.239.32.109
ns-cloud-d2.googledomains.com 216.239.34.109
ns-cloud-d3.googledomains.com 216.239.36.109
ns-cloud-d4.googledomains.com 216.239.38.109
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address