mohammad.com

mohammad.com may not be SSL secured

Free website and domain report on mohammad.com

Last Updated: 30th April, 2020 Update Now
Overview

Snoop Summary for mohammad.com

This is a free and comprehensive report about mohammad.com. The domain mohammad.com is currently hosted on a server located in United States with the IP address 98.124.199.93, where USD is the local currency and the local language is English. Mohammad.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If mohammad.com was to be sold it would possibly be worth $842 USD (based on the daily revenue potential of the website over a 24 month period). Mohammad.com is somewhat popular with an estimated 400 daily unique visitors. This report was last updated 30th April, 2020.

About mohammad.com

Site Preview:
Title:
Description:
Keywords and Tags: parked domain
Related Terms: mohammad, mohammad shokri
Fav Icon:
Age: Over 25 years old
Domain Created: 24th September, 1998
Domain Updated: 12th April, 2018
Domain Expires: 23rd September, 2020
Review

Snoop Score

1/5

Valuation

$842 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 2,848,183
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: 400
Monthly Visitors: 12,175
Yearly Visitors: 146,000
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $35 USD
Yearly Revenue: $416 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: mohammad.com 12
Domain Name: mohammad 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 0.14 seconds
Load Time Comparison: Faster than 99% of sites

PageSpeed Insights

Avg. (All Categories) 47
Performance 0
Accessibility 0
Best Practices 85
SEO 56
Progressive Web App 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
0

Performance

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

Opportunities

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 230 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Avoids enormous network payloads — Total size was 907 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://components.mywebsitebuilder.com/g-201911130911388234/viewer/viewer.js
534382
https://domain4sale.my-free.website/x/cdn/?https://storage.googleapis.com/wzukusers/user-500000/images/Zh7LH2TwaEWkZ-YQlQQbkA_1450.jpg
213403
https://components.mywebsitebuilder.com/websitebuilder/freebanner.html
45773
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
22684
https://components.mywebsitebuilder.com/g-201911130911388234/viewer-website-builder/viewer.css
22541
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
21524
https://www.google-analytics.com/analytics.js
18817
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
16056
https://domain4sale.my-free.website/
7581
https://149b4.wpc.azureedge.net/80149B4/insights/t.js?brand=WebsiteBuilder&v=g-201911130911388234
7126
Uses efficient cache policy on static assets — 1 resource found
Mohammad.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)
https://www.google-analytics.com/analytics.js
7200000
18817
Avoids an excessive DOM size — 1 element
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
1
Maximum DOM Depth
2
Maximum Child Elements
1
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mohammad.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.
Keep request counts low and transfer sizes small — 24 requests • 907 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
24
929258
Script
6
575484
Image
4
214006
Font
3
60264
Document
4
54694
Stylesheet
1
22541
Other
6
2269
Media
0
0
Third-party
23
928605

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.

Other

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://mohammad.com/
0
229.43299985491
653
476
200
text/html
Document
http://web.ez1.com/
244.8040000163
418.52799989283
687
510
200
text/html
Document
http://domain4sale.my-free.website/
431.78700003773
501.80900003761
402
0
301
https://domain4sale.my-free.website/
502.15699989349
820.75099996291
7581
18156
200
text/html
Document
https://149b4.wpc.azureedge.net/80149B4/insights/t.js?brand=WebsiteBuilder&v=g-201911130911388234
832.86500000395
887.7789999824
7126
16324
200
application/javascript
Script
https://components.mywebsitebuilder.com/g-201911130911388234/viewer-website-builder/viewer.css
833.18599988706
859.8050000146
22541
146667
200
text/css
Stylesheet
https://components.mywebsitebuilder.com/g-201911130911388234/viewer/viewer.js
833.34599994123
881.19999994524
534382
2158099
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/5aba222edff21w6mUBDT.js?1577428379
833.57599982992
973.62299985252
6512
27826
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/Z8ChPixWwyvv2Z3jvXDr.js?1577428379
833.72500003316
920.97099986859
4230
32761
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/YRUufKYzcaSbivt8O04k.js?1577428379
834.01099988259
926.86200002208
4417
32177
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
835.47299983911
839.82699993066
18817
45229
200
text/javascript
Script
https://localize.websitebuilder.com/
920.52899999544
1110.1559998933
405
25
200
application/javascript
XHR
1287.0489999186
1287.1619998477
0
4178
200
image/gif
Image
https://components.mywebsitebuilder.com/websitebuilder/freebanner.html
1306.0500000138
1318.8359998167
45773
44966
200
text/html
Document
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
1489.9149998091
1874.4709999301
21524
20544
200
application/x-font-woff
Font
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
1490.1850000024
1591.9729999732
22684
21704
200
application/x-font-woff
Font
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
1490.509999916
1590.2950000018
16056
15076
200
application/x-font-woff
Font
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=1120596181&t=pageview&_s=1&dl=https%3A%2F%2Fdomain4sale.my-free.website%2F&dr=http%3A%2F%2Fweb.ez1.com%2F&ul=en-us&de=UTF-8&dt=Home&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=KEBAAEAB~&jid=1537791745&gjid=1171952086&cid=919009476.1588246962&tid=UA-103171043-2&_gid=512108129.1588246962&_r=1&z=603204694
1586.0639999155
1591.4979998488
603
35
200
image/gif
Image
https://domain4sale.my-free.website/x/cdn/?https://storage.googleapis.com/wzukusers/user-500000/images/Zh7LH2TwaEWkZ-YQlQQbkA_1450.jpg
1586.2579999957
1718.499999959
213403
212193
200
image/jpeg
Image
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
1592.7989999764
1608.7859999388
409
0
200
text/plain
XHR
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
1594.0509999637
1610.0649998989
409
0
200
text/plain
XHR
1652.1860000212
1652.6519998442
0
27253
200
image/svg+xml
Image
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
1680.0009999424
1718.7309998553
322
0
201
text/plain
XHR
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
1680.6689999066
1713.654999854
322
0
201
text/plain
XHR
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.

Metrics

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

Other

Estimated Input Latency
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 mohammad.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
Metrics
Below is a collection of metrics.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mohammad.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Mohammad.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mohammad.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mohammad.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mohammad.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mohammad.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Mohammad.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mohammad.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

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
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.
Minimizes main-thread work
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.
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)
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
384.55600012094
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
101.78799997084
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
99.785000085831
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.
0

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mohammad.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"]`
Mohammad.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mohammad.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Mohammad.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.
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.

Contrast

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

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 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.

Names and labels

Document doesn't have 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.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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 mohammad.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.
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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 3 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://mohammad.com/
http://web.ez1.com/
http://domain4sale.my-free.website/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
56

SEO

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

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.

Content Best Practices

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.

Mobile Friendly

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mohammad.com on mobile screens.

Content Best Practices

Document doesn't have 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.
Failing Elements
Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 10 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<html><head>
Syntax not understood
3
<title></title></head>
Syntax not understood
4
<!-- Redirection Services sjl0vlredir03 -->
Syntax not understood
5
<frameset rows='100%, *' frameborder=no framespacing=0 border=0>
Syntax not understood
6
<frame src="http://web.ez1.com/robots.txt" name=mainwindow frameborder=no framespacing=0 marginheight=0 marginwidth=0></frame>
Unknown directive
7
</frameset>
Syntax not understood
8
<noframes>
Syntax not understood
9
<h2>Your browser does not support frames. We recommend upgrading your browser.</h2><br><br>
Syntax not understood
10
<center>Click <a href="http://web.ez1.com/robots.txt">here</a> to enter the site.</center>
Unknown directive
11
</noframes></html>
Syntax not understood

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.
0

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 mohammad.com. This includes details about web app manifests.

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.

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.
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 — 3 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://mohammad.com/
http://web.ez1.com/
http://domain4sale.my-free.website/
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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mohammad.com on mobile screens.
Does not provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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) 43
Performance 0
Accessibility 0
Best Practices 85
SEO 45
Progressive Web App 0
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
0

Performance

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

Opportunities

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 210 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.

Diagnostics

Avoids enormous network payloads — Total size was 809 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://components.mywebsitebuilder.com/g-201911130911388234/viewer/viewer.js
534370
https://domain4sale.my-free.website/x/cdn/?https://storage.googleapis.com/wzukusers/user-500000/images/Zh7LH2TwaEWkZ-YQlQQbkA_1000.jpg
112840
https://components.mywebsitebuilder.com/websitebuilder/freebanner.html
45749
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
22684
https://components.mywebsitebuilder.com/g-201911130911388234/viewer-website-builder/viewer.css
22519
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
21524
https://www.google-analytics.com/analytics.js
18794
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
16056
https://domain4sale.my-free.website/
7577
https://149b4.wpc.azureedge.net/80149B4/insights/t.js?brand=WebsiteBuilder&v=g-201911130911388234
7126
Uses efficient cache policy on static assets — 1 resource found
Mohammad.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)
https://www.google-analytics.com/analytics.js
7200000
18794
Avoids an excessive DOM size — 1 element
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
1
Maximum DOM Depth
2
Maximum Child Elements
1
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Mohammad.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.
Keep request counts low and transfer sizes small — 23 requests • 809 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
23
828153
Script
6
575422
Image
4
113420
Font
3
60264
Document
4
54666
Stylesheet
1
22519
Other
5
1862
Media
0
0
Third-party
22
827500

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.

Other

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://mohammad.com/
0
204.8459998332
653
476
200
text/html
Document
http://web.ez1.com/
218.34699995816
424.91999990307
687
510
200
text/html
Document
http://domain4sale.my-free.website/
453.37000000291
502.62799998745
401
0
301
https://domain4sale.my-free.website/
503.01399989985
720.62299982645
7577
18091
200
text/html
Document
https://149b4.wpc.azureedge.net/80149B4/insights/t.js?brand=WebsiteBuilder&v=g-201911130911388234
731.92499997094
789.29099999368
7126
16324
200
application/javascript
Script
https://components.mywebsitebuilder.com/g-201911130911388234/viewer-website-builder/viewer.css
732.23500000313
760.03100001253
22519
146667
200
text/css
Stylesheet
https://components.mywebsitebuilder.com/g-201911130911388234/viewer/viewer.js
732.34799993224
859.7609999124
534370
2158099
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/5aba222edff21w6mUBDT.js?1577428379
732.48000000603
1215.5730000231
6492
27826
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/Z8ChPixWwyvv2Z3jvXDr.js?1577428379
732.81299998052
838.30800000578
4230
32761
200
application/javascript
Script
https://storage.googleapis.com/wzukusers/user-14563229/sites/40567829/55a9498b76f2e9afxZjX/YRUufKYzcaSbivt8O04k.js?1577428379
732.94000001624
834.57900001667
4410
32177
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
734.92800001986
739.01799996383
18794
45229
200
text/javascript
Script
https://localize.websitebuilder.com/
823.75099998899
930.56400003843
408
25
200
application/javascript
XHR
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
935.05800003186
947.24899996072
409
0
200
text/plain
XHR
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
949.64899984188
1003.1049998943
322
0
201
text/plain
XHR
1368.0590000004
1368.1989999022
0
4178
200
image/gif
Image
https://components.mywebsitebuilder.com/websitebuilder/freebanner.html
1383.6909998208
1424.8259998858
45749
44966
200
text/html
Document
https://in-us-east-event-hubs.servicebus.windows.net/in-us-east-event-hub-a1/publishers/d73f11cf-b50a-4ee7-80ab-914f4eaa599a/messages?timeout=10
1548.2449999545
1589.6439999342
322
0
201
text/plain
XHR
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
1685.2359999903
2078.3589999191
21524
20544
200
application/x-font-woff
Font
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
1685.5429999996
2211.1769998446
22684
21704
200
application/x-font-woff
Font
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
1685.6809998862
2123.7849998288
16056
15076
200
application/x-font-woff
Font
https://domain4sale.my-free.website/x/cdn/?https://storage.googleapis.com/wzukusers/user-500000/images/Zh7LH2TwaEWkZ-YQlQQbkA_1000.jpg
1821.450999938
1882.6099999715
112840
111566
200
image/jpeg
Image
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=71793176&t=pageview&_s=1&dl=https%3A%2F%2Fdomain4sale.my-free.website%2F&dr=http%3A%2F%2Fweb.ez1.com%2F&ul=en-us&de=UTF-8&dt=Home&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=KEBAAEAB~&jid=585688180&gjid=825663229&cid=1128521996.1588246971&tid=UA-103171043-2&_gid=1290773259.1588246971&_r=1&z=1934318136
1827.7449999005
1831.8900000304
580
35
200
image/gif
Image
1881.9430000149
1882.4310000055
0
27253
200
image/svg+xml
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.

Metrics

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

Other

Estimated Input Latency
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 mohammad.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
Metrics
Below is a collection of metrics.
First Contentful Paint (3G)
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Mohammad.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Mohammad.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Mohammad.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Mohammad.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Mohammad.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Mohammad.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Mohammad.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Mohammad.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

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
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.
Minimizes main-thread work
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.
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)
https://wzuk.blob.core.windows.net/assets/fonts/ALyKWGaVsEemWmMSYxY8yg.woff
393.12299992889
https://wzuk.blob.core.windows.net/assets/fonts/1aJZYUlSkk6puu4aOD3swQ.woff
525.63399984501
https://wzuk.blob.core.windows.net/assets/fonts/qFokD41aVU27THVC-6RMuw.woff
438.10399994254
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.
0

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of mohammad.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"]`
Mohammad.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Mohammad.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Mohammad.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.
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.

Contrast

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

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 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.

Names and labels

Document doesn't have 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.
Failing Elements
`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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 mohammad.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.
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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 3 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://mohammad.com/
http://web.ez1.com/
http://domain4sale.my-free.website/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
45

SEO

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

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.

Content Best Practices

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.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mohammad.com on mobile screens.
Document doesn't use 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 not 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 doesn't have 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.
Failing Elements
Document does not have 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.

Crawling and Indexing

robots.txt is not valid — 10 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.
Line # Content Error
1
<html><head>
Syntax not understood
3
<title></title></head>
Syntax not understood
4
<!-- Redirection Services sjl0vlredir02 -->
Syntax not understood
5
<frameset rows='100%, *' frameborder=no framespacing=0 border=0>
Syntax not understood
6
<frame src="http://web.ez1.com/robots.txt" name=mainwindow frameborder=no framespacing=0 marginheight=0 marginwidth=0></frame>
Unknown directive
7
</frameset>
Syntax not understood
8
<noframes>
Syntax not understood
9
<h2>Your browser does not support frames. We recommend upgrading your browser.</h2><br><br>
Syntax not understood
10
<center>Click <a href="http://web.ez1.com/robots.txt">here</a> to enter the site.</center>
Unknown directive
11
</noframes></html>
Syntax not understood

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.
0

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 mohammad.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.
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 — 3 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://mohammad.com/
http://web.ez1.com/
http://domain4sale.my-free.website/
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
Content is not 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of mohammad.com on mobile screens.
Does not provide fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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: 98.124.199.93
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
eNom, Incorporated
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

Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx/1.10.2
Date: 30th April, 2020
Content-Type: text/html; charset=UTF-8
Content-Length: 476
Connection: close

Whois Lookup

Created: 24th September, 1998
Changed: 12th April, 2018
Expires: 23rd September, 2020
Registrar: ENOM, INC.
Status: clientDeleteProhibited
clientTransferProhibited
Nameservers: dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com
Owner Name: REDACTED FOR PRIVACY
Owner Organization: REDACTED FOR PRIVACY
Owner Street: REDACTED FOR PRIVACY
Owner Post Code: REDACTED FOR PRIVACY
Owner City: REDACTED FOR PRIVACY
Owner State: NV
Owner Country: US
Owner Phone: REDACTED FOR PRIVACY
Owner Email: https://tieredaccess.com/contact/f2dafe26-4e2f-4c61-a7fc-cdc937279de0
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Post Code: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Post Code: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Full Whois:

Domain Name: mohammad.com
Registry Domain ID: 2028400_DOMAIN_COM-VRSN
Registrar WHOIS Server: WHOIS.ENOM.COM
Registrar URL: WWW.ENOM.COM
Updated Date: 2018-04-12T01:23:31.00Z
Creation Date: 1998-09-24T04:00:00.00Z
Registrar Registration Expiration Date: 2020-09-23T04:00:00.00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street:
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: NV
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: https://tieredaccess.com/contact/f2dafe26-4e2f-4c61-a7fc-cdc937279de0
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street:
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street:
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
Name Server: DNS5.NAME-SERVICES.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: ABUSE@ENOM.COM
Registrar Abuse Contact Phone: +1.4259744689
URL of the ICANN WHOIS Data Problem Reporting System: HTTP://WDPRS.INTERNIC.NET/
>>> Last update of WHOIS database: 2020-04-30T11:42:38.00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp


The data in this whois database is provided to you for information
purposes only, that is, to assist you in obtaining information about or
related to a domain name registration record. We make this information
available "as is," and do 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)
enable high volume, automated, electronic processes that stress or load
this whois database system providing you this information; or (2) allow,
enable, or otherwise support the transmission of mass unsolicited,
commercial advertising or solicitations via direct mail, electronic
mail, or by telephone. The compilation, repackaging, dissemination or
other use of this data is expressly prohibited without prior written
consent from us.

We reserve the right to modify these terms at any time. By submitting
this query, you agree to abide by these terms.
Version 6.3 4/3/2002

Nameservers

Name IP Address
dns1.name-services.com 64.98.148.137
dns2.name-services.com 216.40.47.201
dns3.name-services.com 64.98.148.138
dns4.name-services.com 216.40.47.202
dns5.name-services.com 64.98.148.139
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5