shahvani.com

shahvani.com is SSL secured

Free website and domain report on shahvani.com

Last Updated: 27th September, 2023 Update Now
Overview

Snoop Summary for shahvani.com

This is a free and comprehensive report about shahvani.com. The domain shahvani.com is currently hosted on a server located in United States with the IP address 104.26.2.17, where the local currency is USD and English is the local language. Our records indicate that shahvani.com is owned/operated by Cloudflare, Inc.. Shahvani.com is expected to earn an estimated $295 USD per day from advertising revenue. The sale of shahvani.com would possibly be worth $215,288 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Shahvani.com is wildly popular with an estimated 69,735 daily unique visitors. This report was last updated 27th September, 2023.

About shahvani.com

Site Preview:
Title: شهوانی
Description: سایت شهوانی، داستان سکسی، عکس سکسی و انجمن سکسی
Keywords and Tags: adult content, pornography, انجمن سکسی, دوستیابی سکسی, شهوانی، داستان سکسی, عکس سکسی
Related Terms:
Fav Icon:
Age: Over 14 years old
Domain Created: 20th October, 2009
Domain Updated: 13th December, 2018
Domain Expires: 20th October, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$215,288 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 17,492
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 30
Moz Page Authority: 45

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 69,735
Monthly Visitors: 2,122,514
Yearly Visitors: 25,453,275
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $295 USD
Monthly Revenue: $8,976 USD
Yearly Revenue: $107,639 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: shahvani.com 12
Domain Name: shahvani 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 3.19 seconds
Load Time Comparison: Faster than 14% of sites

PageSpeed Insights

Avg. (All Categories) 78
Performance 100
Accessibility 100
Best Practices 67
SEO 100
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
100

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 0.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 60 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).
Largest Contentful Paint — 0.6 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.002
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 130 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://shahvani.com/
http/1.1
0
50.021000031848
678
0
301
text/plain
https://shahvani.com/
h2
50.35700002918
222.17600001022
3415
5909
200
text/html
Document
https://shahvani.com/static/css/all.min.css
h2
228.20100001991
288.26500003925
12280
47206
200
text/css
Stylesheet
https://shahvani.com/static/js/bundle.css
h2
228.4450000152
283.06099999463
2098
4354
200
text/css
Stylesheet
https://shahvani.com/static/images/logo.png
h2
238.45599999186
281.11700003501
6075
5318
200
image/webp
Image
https://shahvani.com/static/js/jquery-3.5.1.min.js
h2
236.80700000841
296.01900000125
32637
89476
200
application/javascript
Script
https://shahvani.com/static/js/moment.js
h2
237.04899998847
300.8409999893
35372
150852
200
application/javascript
Script
https://shahvani.com/static/js/underscore-min.js
h2
237.19200002961
282.12400001939
6133
15626
200
application/javascript
Script
https://shahvani.com/static/js/global.js
h2
237.55200003507
263.32399999956
2892
8174
200
application/javascript
Script
https://shahvani.com/static/js/lp.js
h2
237.74100001901
265.14999999199
1410
1891
200
application/javascript
Script
https://shahvani.com/static/js/sharer.min.js
h2
237.96300002141
296.47800000384
2834
7760
200
application/javascript
Script
https://huskyzipper.com/c2/c0/92/c2c09229fcfd910861168f18aba927c4.js
http/1.1
238.33399999421
1231.3900000299
741
0
500
text/html
Script
https://shahvani.com/static/fonts/Vazir.woff
h2
293.11299999245
320.92700002249
48633
47988
200
application/font-woff
Font
https://www.google-analytics.com/analytics.js
h2
353.16400002921
357.23700001836
20594
50234
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=1453521062&t=pageview&_s=1&dl=https%3A%2F%2Fshahvani.com%2F&ul=en-us&de=UTF-8&dt=%D8%B4%D9%87%D9%88%D8%A7%D9%86%DB%8C&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAEABAAAAACAAI~&jid=387185089&gjid=723526869&cid=720601656.1677845510&tid=UA-11536241-1&_gid=789531551.1677845510&_r=1&_slc=1&z=1847892776
h2
383.69200000307
388.00300000003
497
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-11536241-1&cid=720601656.1677845510&jid=387185089&gjid=723526869&_gid=789531551.1677845510&_u=IEBAAEAAAAAAACAAI~&z=688186410
h2
390.51600004314
396.69700001832
568
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j99&tid=UA-11536241-1&cid=720601656.1677845510&jid=387185089&_u=IEBAAEAAAAAAACAAI~&z=2144528123
h2
398.7339999876
407.18300000299
557
42
200
image/gif
Image
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1677844800
h2
1243.3230000315
1316.4470000193
12217
27196
200
application/javascript
Script
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
h2
1329.6630000114
1351.3590000221
3881
6860
200
application/javascript
Other
https://shahvani.com/cdn-cgi/challenge-platform/h/b/cv/result/7a21c8c6dcc55a76
h2
1699.197000009
1775.6550000049
804
2
200
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.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
226.297
9.985
292.063
16.727
317.467
16.438
340.503
14.015
364.598
20.495
1232.986
9.037
1447.952
252.765
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shahvani.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. Shahvani.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shahvani.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shahvani.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 15 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shahvani.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/js/moment.js
35372
14982
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shahvani.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/css/all.min.css
12280
11662
Reduce unused JavaScript — Potential savings of 47 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/js/moment.js
35372
25300
https://shahvani.com/static/js/jquery-3.5.1.min.js
32637
22707
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 170 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://shahvani.com/
172.81
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Shahvani.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shahvani.com/
190
https://shahvani.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shahvani.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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 190 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://shahvani.com/static/fonts/Vazir.woff
48633
https://shahvani.com/static/js/moment.js
35372
https://shahvani.com/static/js/jquery-3.5.1.min.js
32637
https://www.google-analytics.com/analytics.js
20594
https://shahvani.com/static/css/all.min.css
12280
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1677844800
12217
https://shahvani.com/static/js/underscore-min.js
6133
https://shahvani.com/static/images/logo.png
6075
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/pica.js
3881
https://shahvani.com/
3415
Avoids an excessive DOM size — 69 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
69
Maximum DOM Depth
9
Maximum Child Elements
19
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Shahvani.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.3 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)
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1677844800
257.488
244.154
2.129
https://shahvani.com/
51.544
11.607
3.001
Minimizes main-thread work — 0.4 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)
Script Evaluation
299.261
Other
34.358
Style & Layout
19.031
Script Parsing & Compilation
11.769
Parse HTML & CSS
9.493
Garbage Collection
9.405
Rendering
2.818
Keep request counts low and transfer sizes small — 20 requests • 190 KiB
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
20
194316
Script
9
114830
Font
1
48633
Stylesheet
2
14378
Image
2
6632
Other
5
6428
Document
1
3415
Media
0
0
Third-party
5
22957
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21091
0
568
0
557
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0016711547914671
0.00014085808702662
2.9345434797212E-5
2.8592987751129E-5
2.6335646612882E-5
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.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1677844800
676
126
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 shahvani.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

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.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Serve static assets with an efficient cache policy — 12 resources found
Shahvani.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) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20594
https://shahvani.com/cdn-cgi/challenge-platform/h/b/scripts/alpha/invisible.js?ts=1677844800
14400000
12217
https://shahvani.com/static/fonts/Vazir.woff
432000000
48633
https://shahvani.com/static/js/moment.js
432000000
35372
https://shahvani.com/static/js/jquery-3.5.1.min.js
432000000
32637
https://shahvani.com/static/css/all.min.css
432000000
12280
https://shahvani.com/static/js/underscore-min.js
432000000
6133
https://shahvani.com/static/images/logo.png
432000000
6075
https://shahvani.com/static/js/global.js
432000000
2892
https://shahvani.com/static/js/sharer.min.js
432000000
2834
https://shahvani.com/static/js/bundle.css
432000000
2098
https://shahvani.com/static/js/lp.js
432000000
1410

Other

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://shahvani.com/static/fonts/Vazir.woff
27.814000030048
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://shahvani.com/static/images/logo.png
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of shahvani.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.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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 alternate 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>`, `<template>` or `<div>` 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.
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.

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.

Best practices

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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Shahvani.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

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

Audits

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 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Underscore
1.7.0
Moment.js
2.24.0
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://shahvani.com/static/js/underscore-min.js
https://shahvani.com/static/js/underscore-min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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 Request Resolution
http://shahvani.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
1
Medium
1
High

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
...
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.
Source Description
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for shahvani.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 shahvani.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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered 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.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of shahvani.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.
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 shahvani.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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) 74
Performance 76
Accessibility 100
Best Practices 67
SEO 98
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://shahvani.com/
Updated: 3rd March, 2023

1.97 seconds
First Contentful Paint (FCP)
73%
10%
17%

0.01 seconds
First Input Delay (FID)
96%
2%
2%

76

Performance

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

Metrics

First Contentful Paint — 1.6 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.7 s
The time taken for the page to become fully interactive.
Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.025
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.6 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://shahvani.com/
http/1.1
0
36.32000007201
672
0
301
text/plain
https://shahvani.com/
h2
36.778000066988
167.40300005767
3415
5909
200
text/html
Document
https://shahvani.com/static/css/all.min.css
h2
179.62100007571
209.40900000278
12282
47206
200
text/css
Stylesheet
https://shahvani.com/static/js/bundle.css
h2
180.21899997257
206.47600002121
2102
4354
200
text/css
Stylesheet
https://shahvani.com/static/images/logo.png
h2
189.43999998737
261.84200006537
6073
5318
200
image/webp
Image
https://shahvani.com/static/js/jquery-3.5.1.min.js
h2
186.84600002598
231.44100001082
32631
89476
200
application/javascript
Script
https://shahvani.com/static/js/moment.js
h2
187.61400005314
250.42300007772
35368
150852
200
application/javascript
Script
https://shahvani.com/static/js/underscore-min.js
h2
187.99900007434
226.32700006943
6139
15626
200
application/javascript
Script
https://shahvani.com/static/js/global.js
h2
188.42300004326
215.93599999323
2894
8174
200
application/javascript
Script
https://shahvani.com/static/js/lp.js
h2
188.56200005393
248.47800005227
1412
1891
200
application/javascript
Script
https://shahvani.com/static/js/sharer.min.js
h2
188.82200005464
217.21200004686
2836
7760
200
application/javascript
Script
https://huskyzipper.com/c2/c0/92/c2c09229fcfd910861168f18aba927c4.js
http/1.1
188.98199999239
953.71999999043
741
0
500
text/html
Script
https://shahvani.com/static/fonts/Vazir.woff
h2
221.04900004342
260.77200006694
48639
47988
200
application/font-woff
Font
https://www.google-analytics.com/analytics.js
h2
335.60600003693
341.36600000784
20594
50234
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j99&a=944422748&t=pageview&_s=1&dl=https%3A%2F%2Fshahvani.com%2F&ul=en-us&de=UTF-8&dt=%D8%B4%D9%87%D9%88%D8%A7%D9%86%DB%8C&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAEABAAAAACAAI~&jid=1191941897&gjid=2076917000&cid=1769942349.1677845526&tid=UA-11536241-1&_gid=2131090798.1677845526&_r=1&_slc=1&z=1169421079
h2
376.65400002152
381.13400002476
497
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j99&tid=UA-11536241-1&cid=1769942349.1677845526&jid=1191941897&gjid=2076917000&_gid=2131090798.1677845526&_u=IEBAAEAAAAAAACAAI~&z=1603380166
h2
384.62200004142
388.89599998947
568
2
200
text/plain
XHR
https://www.google.com/ads/ga-audiences?t=sr&aip=1&_r=4&slf_rd=1&v=1&_v=j99&tid=UA-11536241-1&cid=1769942349.1677845526&jid=1191941897&_u=IEBAAEAAAAAAACAAI~&z=1789278365
h2
391.93200005684
402.69100002479
557
42
200
image/gif
Image
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1677844800
h2
969.84799997881
996.74500001129
15173
35292
200
application/javascript
Script
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
h2
1016.4840000216
1045.6959999865
8826
20136
200
application/javascript
Other
https://shahvani.com/cdn-cgi/challenge-platform/h/g/cv/result/7a21c927fcdd2069
h2
2250.6379999686
2296.1610000348
830
2
200
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.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
173.088
13.669
216.384
49.874
279.144
5.757
285.805
7.382
293.198
18.271
314.455
22.04
349.381
29.235
955.662
11.71
1009.871
6.849
1792.157
459.852
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Shahvani.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Shahvani.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Shahvani.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 15 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Shahvani.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/js/moment.js
35368
14981
Reduce unused CSS — Potential savings of 11 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Shahvani.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/css/all.min.css
12282
11340
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 130 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://shahvani.com/
131.595
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Shahvani.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://shahvani.com/
630
https://shahvani.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Shahvani.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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 198 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://shahvani.com/static/fonts/Vazir.woff
48639
https://shahvani.com/static/js/moment.js
35368
https://shahvani.com/static/js/jquery-3.5.1.min.js
32631
https://www.google-analytics.com/analytics.js
20594
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1677844800
15173
https://shahvani.com/static/css/all.min.css
12282
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/pica.js
8826
https://shahvani.com/static/js/underscore-min.js
6139
https://shahvani.com/static/images/logo.png
6073
https://shahvani.com/
3415
Avoids an excessive DOM size — 69 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
69
Maximum DOM Depth
9
Maximum Child Elements
19
Avoid chaining critical requests — 9 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Shahvani.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.
Keep request counts low and transfer sizes small — 20 requests • 198 KiB
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
20
202249
Script
9
117788
Font
1
48639
Stylesheet
2
14384
Other
5
11393
Image
2
6630
Document
1
3415
Media
0
0
Third-party
5
22957
Minimize third-party usage — Third-party code blocked the main thread for 60 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21091
59.012
568
0
557
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.019889573832505
0.0043679064102755
0.00077608337111145
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.
Avoid long main-thread tasks — 6 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1677844800
2711
920
https://www.google-analytics.com/analytics.js
3631
117
https://shahvani.com/
1165
100
https://shahvani.com/static/js/moment.js
2610
88
https://shahvani.com/static/js/jquery-3.5.1.min.js
2160
73
https://shahvani.com/
1110
55
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 shahvani.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

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.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 350 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Shahvani.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://shahvani.com/static/css/all.min.css
12282
150
Reduce unused JavaScript — Potential savings of 47 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://shahvani.com/static/js/moment.js
35368
25297
https://shahvani.com/static/js/jquery-3.5.1.min.js
32631
22703
Serve static assets with an efficient cache policy — 12 resources found
Shahvani.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) Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
20594
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1677844800
14400000
15173
https://shahvani.com/static/fonts/Vazir.woff
432000000
48639
https://shahvani.com/static/js/moment.js
432000000
35368
https://shahvani.com/static/js/jquery-3.5.1.min.js
432000000
32631
https://shahvani.com/static/css/all.min.css
432000000
12282
https://shahvani.com/static/js/underscore-min.js
432000000
6139
https://shahvani.com/static/images/logo.png
432000000
6073
https://shahvani.com/static/js/global.js
432000000
2894
https://shahvani.com/static/js/sharer.min.js
432000000
2836
https://shahvani.com/static/js/bundle.css
432000000
2102
https://shahvani.com/static/js/lp.js
432000000
1412
Reduce JavaScript execution time — 2.1 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)
https://shahvani.com/cdn-cgi/challenge-platform/h/g/scripts/alpha/invisible.js?ts=1677844800
1878.64
1809.768
9.848
https://shahvani.com/
390.94
63.788
16.048
Unattributable
175.228
7.692
0
https://www.google-analytics.com/analytics.js
138.96
122.272
4.656
https://shahvani.com/static/js/jquery-3.5.1.min.js
86.18
71.576
7.464
Minimize main-thread work — 2.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)
Script Evaluation
2113.504
Other
244.616
Style & Layout
211.992
Script Parsing & Compilation
57.1
Garbage Collection
50.372
Parse HTML & CSS
45.048
Rendering
21.344
First Contentful Paint (3G) — 3060 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Metrics

Total Blocking Time — 1,000 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).

Audits

Max Potential First Input Delay — 920 ms
Users could experience a delay when interacting with the page.

Other

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://shahvani.com/static/fonts/Vazir.woff
39.723000023514
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://shahvani.com/static/images/logo.png
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of shahvani.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.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<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 alternate 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>`, `<template>` or `<div>` 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.
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.

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.

Best practices

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.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Shahvani.com may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Best Practices

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

Audits

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 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
Underscore
1.7.0
Moment.js
2.24.0
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://shahvani.com/static/js/underscore-min.js
https://shahvani.com/static/js/underscore-min.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request 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 Request Resolution
http://shahvani.com/
Allowed
Includes front-end JavaScript libraries with known security vulnerabilities — 2 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
1
Medium
1
High

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
...
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.
Source Description
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
98

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for shahvani.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 shahvani.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
100.00%
≥ 12px

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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered 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.

Mobile Friendly

Tap targets are not sized appropriately — 88% 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.
Tap Target Size Overlapping Target
21x18

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of shahvani.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.
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 shahvani.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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: 104.26.2.17
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
Cloudflare, Inc.
Registration

Domain Registrant

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

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.99.56
Security

Visitor Safety

Mature Content: Yes
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 38/100
WOT Child Safety: 15/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 15th April, 2023
Valid To: 14th April, 2024
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 8870940217161680885973612654744781313
Serial Number (Hex): 06AC7B1EE0C116690CADB1E801974201
Valid From: 15th April, 2024
Valid To: 14th April, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Apr 15 02:00:48.151 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:33:E9:2D:B4:43:5D:AD:D2:A6:F5:0B:B2:
41:F0:10:AA:55:28:59:C6:75:AA:14:FE:BF:F1:34:AC:
DB:EB:86:62:02:20:45:F0:7A:7A:F9:24:33:0A:E1:3B:
A8:8E:75:35:1D:DD:3A:1C:A0:6D:4F:09:9B:DB:6D:03:
E0:1F:80:E5:F5:16
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Apr 15 02:00:48.201 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:A5:4F:45:59:CC:85:BB:6F:7A:67:71:
CD:DD:D7:FF:42:98:82:B8:9B:21:0E:E7:31:06:01:0E:
BB:6A:53:75:1C:02:20:16:8D:3B:53:2E:C4:68:65:73:
DF:2F:07:8B:D2:B6:C7:86:8A:B7:2E:62:6A:89:B3:3E:
47:DE:3F:86:85:06:2A
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Apr 15 02:00:48.164 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:DB:AB:DF:A3:F0:B4:63:DC:F9:A0:CE:
BC:00:98:47:08:1D:F3:1A:D9:2C:96:D8:51:A3:5B:36:
3D:2E:AC:D6:27:02:21:00:E7:99:00:53:93:E9:EC:06:
72:EF:05:D0:09:07:5F:4B:7E:9B:1B:BC:58:E8:3D:06:
55:56:EE:87:A6:4F:AD:AD
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.shahvani.com
DNS:sni.cloudflaressl.com
DNS:shahvani.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 405 Method Not Allowed
Date: 30th April, 2023
Content-Type: text/plain; charset=utf-8
Allow: GET, OPTIONS
Server: cloudflare
Content-Length: 19
Connection: keep-alive
X-Content-Type-Options: nosniff
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=s6xi2o%2FH5GKt%2FSBehbk6fvKEzedAtEUX8bhl12ru9y7jhAT9hk%2FUe3TZ%2FFNlW2gRTIkwe9%2B13AHdE08BnudGi9ZAj%2F5BHTy%2FkR4wqc7OlvM3t%2BdnAe2ILeI2TfWmCQ%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7c0380130cf1c420-EWR

Whois Lookup

Created: 20th October, 2009
Changed: 13th December, 2018
Expires: 20th October, 2023
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: dina.ns.cloudflare.com
hank.ns.cloudflare.com
Owner Name: Redacted for Privacy
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Full Whois: Domain name: shahvani.com
Registry Domain ID: 1572853062_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2018-12-13T17:40:03.00Z
Creation Date: 2009-10-20T01:47:34.00Z
Registrar Registration Expiration Date: 2023-10-20T01:47:34.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: b4662482d0914ab9b8486fd3d27ab6e9.protect@withheldforprivacy.com
Name Server: dina.ns.cloudflare.com
Name Server: hank.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-04-30T21:55:35.68Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
dina.ns.cloudflare.com 173.245.58.107
hank.ns.cloudflare.com 108.162.193.116
Related

Subdomains

Domain Subdomain
up

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address