forosdz.com

forosdz.com is SSL secured

Free website and domain report on forosdz.com

Last Updated: 12th October, 2023 Update Now
Overview

Snoop Summary for forosdz.com

This is a free and comprehensive report about forosdz.com. Our records indicate that forosdz.com is privately registered by Privacy service provided by Withheld for Privacy ehf. Forosdz.com is expected to earn an estimated $19 USD per day from advertising revenue. The sale of forosdz.com would possibly be worth $14,018 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Forosdz.com receives an estimated 6,733 unique visitors every day - a huge amount of traffic! This report was last updated 12th October, 2023.

About forosdz.com

Site Preview:
Title:
Description: Una comunidad de anime, manga, hentai, videojuegos y mas...
Keywords and Tags: adult content, bulletin boards, forum, popular
Related Terms: atomix videojuegos, videojuegos, videojuegos pc
Fav Icon:
Age: Over 19 years old
Domain Created: 22nd May, 2004
Domain Updated: 25th May, 2022
Domain Expires: 22nd May, 2023
Review

Snoop Score

3/5 (Great!)

Valuation

$14,018 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 66,994
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 54
Moz Page Authority: 47

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,733
Monthly Visitors: 204,931
Yearly Visitors: 2,457,545
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $19 USD
Monthly Revenue: $584 USD
Yearly Revenue: $7,004 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: forosdz.com 11
Domain Name: forosdz 7
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.33 seconds
Load Time Comparison: Faster than 57% of sites

PageSpeed Insights

Avg. (All Categories) 75
Performance 98
Accessibility 89
Best Practices 83
SEO 82
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
98

Performance

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

Metrics

First Contentful Paint — 0.8 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.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 20 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.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.012
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 80 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 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://forosdz.com/
http/1.1
0
190.02899999032
6128
11380
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
202.14899998973
225.51699998439
53275
144176
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
202.29600000312
252.22899997607
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
http/1.1
202.41499997792
237.10099997697
1023
1260
200
text/css
Stylesheet
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
h2
245.64499998814
320.79800000065
6377
5961
200
image/svg+xml
Image
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
245.50399999134
280.58399999281
7454
7000
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/arrows.png
http/1.1
256.39199998113
282.37499998068
11817
11375
200
image/png
Image
http://forosdz.com/track.php?domain=forosdz.com&toggle=browserjs&uid=MTY1MzM1Nzc5MS41MTcxOmYyMmY3NTRkNjVhNDZhYzQwNGU3MjE2OTNkYjE1OGEyOWIyODllNTkyNjM0ODU5YjFjYzIyZjBhNWYyNDBjZGU6NjI4YzNjZGY3ZTNjNw%3D%3D
http/1.1
287.03700000187
422.99699998694
608
0
200
text/html
XHR
http://forosdz.com/ls.php
http/1.1
425.3439999884
584.32399999583
861
0
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=forosdz.com&client=dp-teaminternet04_3ph&product=SAS&callback=__sasCookie
h2
430.79600000056
435.85700000403
822
188
200
text/javascript
Script
https://www.google.com/afs/ads?adtest=off&psid=1420240428&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2744431292869648&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300953%2C17300956&format=r5%7Cs&nocache=1541653357791806&num=0&output=afd_ads&domain_name=forosdz.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1653357791807&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=822&frm=0&uio=--&cont=tc&jsid=caf&jsv=14372&rurl=http%3A%2F%2Fforosdz.com%2F
h2
441.08199997572
536.73599998001
2573
6058
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
548.71000000276
565.74499999988
53325
144142
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
597.7819999971
601.05299999123
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
597.87299999152
601.58699998283
1090
200
200
image/svg+xml
Image
http://forosdz.com/track.php?domain=forosdz.com&caf=1&toggle=answercheck&answer=yes&uid=MTY1MzM1Nzc5MS41MTcxOmYyMmY3NTRkNjVhNDZhYzQwNGU3MjE2OTNkYjE1OGEyOWIyODllNTkyNjM0ODU5YjFjYzIyZjBhNWYyNDBjZGU6NjI4YzNjZGY3ZTNjNw%3D%3D
http/1.1
601.85300000012
738.8369999826
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=g5rzpc7kdk2x&aqid=3zyMYvXWNMqQ0_wPvPup4AY&psid=1420240428&pbt=bs&adbx=410&adby=178&adbh=797&adbw=530&adbah=156%2C156%2C156%2C156%2C156&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=14372333520056218109&csadii=7&csadr=331&csala=7%7C112%7C31%7C188&lle=0&llm=1000&ifv=1&usr=1
h2
2271.6819999914
2297.3839999759
332
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=zf9spxhw1622&aqid=3zyMYvXWNMqQ0_wPvPup4AY&psid=1420240428&pbt=bv&adbx=410&adby=178&adbh=797&adbw=530&adbah=156%2C156%2C156%2C156%2C156&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=14372333520056218109&csadii=7&csadr=331&csala=7%7C112%7C31%7C188&lle=0&llm=1000&ifv=1&usr=1
h2
2772.3619999888
2796.7899999931
332
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
239.084
6.245
282.613
9.088
301.14
5.756
327.916
161.501
585.533
7.061
621.186
24.517
646.262
139.293
785.569
7.583
802.103
6.709
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. Forosdz.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Forosdz.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Forosdz.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Forosdz.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Forosdz.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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 190 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)
http://forosdz.com/
191.021
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Forosdz.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Forosdz.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 — Potential savings of 110 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/arrows.png
110
Avoids enormous network payloads — Total size was 145 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=0
53325
http://www.google.com/adsense/domains/caf.js
53275
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/arrows.png
11817
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
6377
http://forosdz.com/
6128
https://www.google.com/afs/ads?adtest=off&psid=1420240428&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2744431292869648&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300953%2C17300956&format=r5%7Cs&nocache=1541653357791806&num=0&output=afd_ads&domain_name=forosdz.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1653357791807&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=822&frm=0&uio=--&cont=tc&jsid=caf&jsv=14372&rurl=http%3A%2F%2Fforosdz.com%2F
2573
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1090
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
1023
Uses efficient cache policy on static assets — 7 resources found
Forosdz.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/arrows.png
0
11817
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
0
6377
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
0
1023
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 38 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
38
Maximum DOM Depth
7
Maximum Child Elements
16
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Forosdz.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.4 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)
http://www.google.com/adsense/domains/caf.js
158.486
152.657
2.71
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
141.572
141.15
0.226
https://www.google.com/adsense/domains/caf.js?pac=0
123.365
90.663000000001
2.263
Minimizes main-thread work — 0.5 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
410.239
Other
56.599
Style & Layout
13.022
Rendering
11.974
Script Parsing & Compilation
9.266
Parse HTML & CSS
6.603
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 17 requests • 145 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
17
148642
Script
4
114876
Image
6
21136
Document
2
8701
Other
3
2079
Stylesheet
2
1850
Media
0
0
Font
0
0
Third-party
13
140435
Minimize third-party usage — Third-party code blocked the main thread for 180 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)
27498
88.017
109837
87.527
822
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.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.012346967866211
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 — 2 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)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
500
162
http://www.google.com/adsense/domains/caf.js
662
139
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 forosdz.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 520 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Forosdz.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
190
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
1023
190
http://www.google.com/adsense/domains/caf.js
53275
270
Reduce unused JavaScript — Potential savings of 61 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
53275
31945
https://www.google.com/adsense/domains/caf.js?pac=0
53325
30545

Other

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://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of forosdz.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.
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.

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"]`
Forosdz.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that forosdz.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.
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.
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.
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 9 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 Request Resolution
http://forosdz.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/arrows.png
Allowed
http://forosdz.com/track.php?domain=forosdz.com&toggle=browserjs&uid=MTY1MzM1Nzc5MS41MTcxOmYyMmY3NTRkNjVhNDZhYzQwNGU3MjE2OTNkYjE1OGEyOWIyODllNTkyNjM0ODU5YjFjYzIyZjBhNWYyNDBjZGU6NjI4YzNjZGY3ZTNjNw%3D%3D
Allowed
http://forosdz.com/ls.php
Allowed
http://forosdz.com/track.php?domain=forosdz.com&caf=1&toggle=answercheck&answer=yes&uid=MTY1MzM1Nzc5MS41MTcxOmYyMmY3NTRkNjVhNDZhYzQwNGU3MjE2OTNkYjE1OGEyOWIyODllNTkyNjM0ODU5YjFjYzIyZjBhNWYyNDBjZGU6NjI4YzNjZGY3ZTNjNw%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for forosdz.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 forosdz.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.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

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

Content Best Practices

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

Links are not 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.

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 forosdz.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 forosdz.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 81
Accessibility 89
Best Practices 83
SEO 85
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
81

Performance

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

Metrics

Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
Speed Index — 2.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 50 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).

Other

Properly size images
Images can slow down the page's load time. Forosdz.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Forosdz.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Forosdz.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Forosdz.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Forosdz.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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression — Potential savings of 5 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7000
5173
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 140 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)
http://forosdz.com/
143.872
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Forosdz.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Forosdz.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.
Avoids enormous network payloads — Total size was 137 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js?pac=0
53325
http://www.google.com/adsense/domains/caf.js
53276
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
7454
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
6377
http://forosdz.com/
6017
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/bottom.png
3799
https://www.google.com/afs/ads?adtest=off&psid=1420240428&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2744431292869648&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r5%7Cs&nocache=6221653357803096&num=0&output=afd_ads&domain_name=forosdz.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1653357803097&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=450&frm=0&uio=--&cont=tc&jsid=caf&jsv=14372&rurl=http%3A%2F%2Fforosdz.com%2F
2567
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
1090
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
1023
Uses efficient cache policy on static assets — 7 resources found
Forosdz.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)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
0
7454
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
0
6377
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/bottom.png
0
3799
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
0
1023
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
82800000
1090
Avoids an excessive DOM size — 38 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
38
Maximum DOM Depth
7
Maximum Child Elements
16
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Forosdz.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.
Minimizes main-thread work — 2.0 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
1580.18
Other
224.848
Style & Layout
66.788
Rendering
56.244
Script Parsing & Compilation
35.6
Parse HTML & CSS
34.944
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 17 requests • 137 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
17
140507
Script
4
114876
Image
6
13118
Document
2
8584
Other
3
2079
Stylesheet
2
1850
Media
0
0
Font
0
0
Third-party
13
132411
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.
Element
Avoid large layout shifts — 1 element found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.21923611111111
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 — 3 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)
http://www.google.com/adsense/domains/caf.js
2201
451
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
1860
341
https://www.google.com/adsense/domains/caf.js?pac=0
3090
146
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 forosdz.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.

Audits

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://forosdz.com/
http/1.1
0
142.8780000424
6017
11420
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
http/1.1
154.29999999469
170.23600003449
53276
144167
200
text/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
154.49400001671
199.981999991
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
http/1.1
154.68100004364
202.72200001637
1023
1260
200
text/css
Stylesheet
https://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
h2
188.55500000063
259.40300000366
6377
5961
200
image/svg+xml
Image
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
http/1.1
188.40300000738
238.99000004167
7454
7000
200
application/javascript
Script
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/bottom.png
http/1.1
207.27000001352
265.4910000274
3799
3359
200
image/png
Image
http://forosdz.com/track.php?domain=forosdz.com&toggle=browserjs&uid=MTY1MzM1NzgwMi43OTI0OmIyYWNkOWZkZTA5NGU2YmY5YTIxOGRjZjhlYzE4Mjg2YzgzNTUxOTVmNDg0ODZhMjczYjQyYWZlM2Q3YWFmZjQ6NjI4YzNjZWFjMTczMA%3D%3D
http/1.1
243.90900001163
387.68300000811
608
0
200
text/html
XHR
http://forosdz.com/ls.php
http/1.1
389.99100000365
498.82000003709
861
0
201
text/javascript
XHR
https://partner.googleadservices.com/gampad/cookie.js?domain=forosdz.com&client=dp-teaminternet04_3ph&product=SAS&callback=__sasCookie
h2
394.89100000355
400.19700000994
821
188
200
text/javascript
Script
https://www.google.com/afs/ads?adtest=off&psid=1420240428&pcsa=false&channel=000002%2Cbucket003&client=dp-teaminternet04_3ph&r=m&hl=en&max_radlink_len=40&type=3&uiopt=true&swp=as-drid-2744431292869648&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300953%2C17300956&format=r5%7Cs&nocache=6221653357803096&num=0&output=afd_ads&domain_name=forosdz.com&v=3&bsl=8&pac=0&u_his=2&u_tz=-420&dt=1653357803097&u_w=360&u_h=640&biw=360&bih=640&psw=360&psh=450&frm=0&uio=--&cont=tc&jsid=caf&jsv=14372&rurl=http%3A%2F%2Fforosdz.com%2F
h2
408.13600004185
501.97800004389
2567
6059
200
text/html
Document
https://www.google.com/adsense/domains/caf.js?pac=0
h2
514.56700003473
530.90100002009
53325
144142
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
574.64599999366
578.96499999333
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/chevron.svg?c=%23ffffff
h2
574.86600003904
581.77400002023
1090
200
200
image/svg+xml
Image
http://forosdz.com/track.php?domain=forosdz.com&caf=1&toggle=answercheck&answer=yes&uid=MTY1MzM1NzgwMi43OTI0OmIyYWNkOWZkZTA5NGU2YmY5YTIxOGRjZjhlYzE4Mjg2YzgzNTUxOTVmNDg0ODZhMjczYjQyYWZlM2Q3YWFmZjQ6NjI4YzNjZWFjMTczMA%3D%3D
http/1.1
583.49000004819
690.71200001054
610
0
200
text/html
XHR
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=s83o9floxh8&aqid=6zyMYsucCcH1owbW0pCwBg&psid=1420240428&pbt=bs&adbx=30&adby=158&adbh=849&adbw=300&adbah=182%2C156%2C156%2C182%2C156&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=14372333520056218109&csadii=7&csadr=318&csala=7%7C113%7C34%7C171&lle=0&llm=1000&ifv=1&usr=1
h2
2222.5700000417
2251.3400000171
332
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-teaminternet04_3ph&output=uds_ads_only&zx=fa9tz7l20rvi&aqid=6zyMYsucCcH1owbW0pCwBg&psid=1420240428&pbt=bv&adbx=30&adby=158&adbh=849&adbw=300&adbah=182%2C156%2C156%2C182%2C156&adbn=master-1&eawp=partner-dp-teaminternet04_3ph&errv=14372333520056218109&csadii=7&csadr=318&csala=7%7C113%7C34%7C171&lle=0&llm=1000&ifv=1&usr=1
h2
2722.9880000232
2745.2820000472
332
0
204
text/html
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
196.259
6.988
230.948
8.293
256.024
13.365
290.953
170.298
555.14
6.332
591.741
36.606
629.038
112.703
741.76
6.917
755.72
5.454
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.

Metrics

First Contentful Paint — 2.8 s
The time taken for the first image or text on the page to be rendered.
Largest Contentful Paint — 3.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.219
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 2.8 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 61 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
http://www.google.com/adsense/domains/caf.js
53276
31947
https://www.google.com/adsense/domains/caf.js?pac=0
53325
30537
Preload Largest Contentful Paint image — Potential savings of 330 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/bottom.png
330
Reduce JavaScript execution time — 1.6 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)
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
590.648
589.136
0.82
http://www.google.com/adsense/domains/caf.js
524.12
501.016
9.688
https://www.google.com/adsense/domains/caf.js?pac=0
500.3
381.532
10.044
http://forosdz.com/
217.652
89.892
8.768
Unattributable
105.696
9.32
0.552

Audits

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

Other

Eliminate render-blocking resources — Potential savings of 1,980 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Forosdz.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)
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
630
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
1023
630
http://www.google.com/adsense/domains/caf.js
53276
1080
Reduce the impact of third-party code — Third-party code blocked the main thread for 960 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)
19480
532.536
109832
430.032
821
0
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://d1lxhc4jvstzrp.cloudfront.net/themes/registrar/images/namecheap1.svg
First Contentful Paint (3G) — 5428 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
89

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of forosdz.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.
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.

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"]`
Forosdz.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Names and labels

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that forosdz.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.
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.
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.
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 9 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 Request Resolution
http://forosdz.com/
Allowed
http://www.google.com/adsense/domains/caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/scripts/js3caf.js
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/regnitz_0f823431/img/bottom.png
Allowed
http://forosdz.com/track.php?domain=forosdz.com&toggle=browserjs&uid=MTY1MzM1NzgwMi43OTI0OmIyYWNkOWZkZTA5NGU2YmY5YTIxOGRjZjhlYzE4Mjg2YzgzNTUxOTVmNDg0ODZhMjczYjQyYWZlM2Q3YWFmZjQ6NjI4YzNjZWFjMTczMA%3D%3D
Allowed
http://forosdz.com/ls.php
Allowed
http://forosdz.com/track.php?domain=forosdz.com&caf=1&toggle=answercheck&answer=yes&uid=MTY1MzM1NzgwMi43OTI0OmIyYWNkOWZkZTA5NGU2YmY5YTIxOGRjZjhlYzE4Mjg2YzgzNTUxOTVmNDg0ODZhMjczYjQyYWZlM2Q3YWFmZjQ6NjI4YzNjZWFjMTczMA%3D%3D
Allowed

Audits

Uses deprecated APIs — 1 warning found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for forosdz.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 forosdz.com on mobile screens.
Document uses legible font sizes — 95.74% 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
.si133
4.26%
11px
95.74%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

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

Links are not 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.

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 forosdz.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 forosdz.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.21.234.116
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Redacted for Privacy
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: Reykjavik
State: Capital Region
Post Code: 101
Email: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.protect@withheldforprivacy.com
Phone: +354.4212434
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: 85/100
WOT Child Safety: 34/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: forosdz.com
Issued By: GTS CA 1P5
Valid From: 15th April, 2023
Valid To: 14th July, 2023
Subject: CN = forosdz.com
Hash: d17a7ae4
Issuer: CN = GTS CA 1P5
O = Google Trust Services LLC
S = US
Version: 2
Serial Number: 0xDAEAD4A213B8C4101109B157B191C0CA
Serial Number (Hex): DAEAD4A213B8C4101109B157B191C0CA
Valid From: 15th April, 2024
Valid To: 14th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:D5:FC:9E:0D:DF:1E:CA:DD:08:97:97:6E:2B:C5:5F:C5:2B:F5:EC:B8
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crls.pki.goog/gts1p5/Cn4EaIf2FJk.crl

Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.11129.2.5.3

Authority Information Access: OCSP - URI:http://ocsp.pki.goog/s/gts1p5/oPAZqrlAMWo
CA Issuers - URI:http://pki.goog/repo/certs/gts1p5.der

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : Apr 15 01:50:49.359 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:45:17:7D:06:4D:50:44:E0:A6:C0:F5:40:
FD:68:BC:95:67:37:86:13:FF:A9:85:D3:AE:9D:DA:2A:
36:90:8D:0E:02:20:33:EB:E0:1C:AF:DE:B7:AF:7F:4E:
3E:CE:BF:ED:00:EF:65:54:40:7A:12:11:E3:00:47:F2:
43:C5:08:10:E9:4E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Apr 15 01:50:48.383 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:58:E0:EE:E3:FB:A2:95:DC:2A:36:06:EF:
D1:B4:BB:83:D9:AB:FB:64:AC:DF:35:8A:DC:0F:23:D5:
77:EA:DC:47:02:20:42:DF:94:2C:74:D4:81:9D:7D:53:
DD:8A:87:89:8D:96:C9:D6:B6:FE:15:EA:05:D5:9F:0E:
99:F0:D0:EC:D5:38
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.forosdz.com
DNS:forosdz.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
forosdz.com. 99.83.154.118 IN 600

NS Records

Host Nameserver Class TTL
forosdz.com. dns101.registrar-servers.com. IN 3600
forosdz.com. dns102.registrar-servers.com. IN 3600
forosdz.com. dns2.registrar-servers.com. IN 3600
forosdz.com. dns1.registrar-servers.com. IN 3600

MX Records

Priority Host Server Class TTL
5 forosdz.com. mail.h-email.net. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
forosdz.com. dns101.registrar-servers.com. hostmaster.forosdz.com. 10800

TXT Records

Host Value Class TTL
forosdz.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 24th May, 2022
Content-Type: text/html; charset=UTF-8
Server: nginx
Connection: keep-alive
Vary: Accept-Encoding
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_aJ/San8RA66SpCDjKEr5Af+aTUbY4UvTr/0Q5RBC7rEWaNITvXEHCoQeglKAXmBLjIO3Vmat0RLuOzcpfZaNmw==
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30

Whois Lookup

Created: 22nd May, 2004
Changed: 25th May, 2022
Expires: 22nd May, 2023
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
Nameservers: dave.ns.cloudflare.com
may.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.protect@withheldforprivacy.com
Full Whois: Domain name: forosdz.com
Registry Domain ID: 120743145_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2022-05-25T00:47:46.61Z
Creation Date: 2004-05-22T06:54:08.00Z
Registrar Registration Expiration Date: 2023-05-22T06:54:08.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.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: 2a43cdd1cdfd44bbab2ed0ffc7a9e4a1.protect@withheldforprivacy.com
Name Server: dave.ns.cloudflare.com
Name Server: may.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-20T12:18:10.97Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
dave.ns.cloudflare.com 108.162.193.109
may.ns.cloudflare.com 172.64.32.135
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$867 USD 2/5
$3,632 USD 2/5
$1,490,595 USD 4/5
$3,655 USD 2/5
$405 USD

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5

Sites hosted on the same IP address