for.com

for.com may not be SSL secured

Free website and domain report on for.com

Last Updated: 12th November, 2022 Update Now
Overview

Snoop Summary for for.com

This is a free and comprehensive report about for.com. For.com is hosted in Ashburn, Virginia in United States on a server with an IP address of 23.23.86.44, where USD is the local currency and the local language is English. For.com has the potential to be earning an estimated $1 USD per day from advertising revenue. If for.com was to be sold it would possibly be worth $749 USD (based on the daily revenue potential of the website over a 24 month period). For.com receives an estimated 355 unique visitors every day - a decent amount of traffic! This report was last updated 12th November, 2022.

About for.com

Site Preview: for.com for.com
Title: For.com
Description:
Keywords and Tags: internet services, spam
Related Terms:
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

Valuation

$749 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 3,683,741
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 355
Monthly Visitors: 10,807
Yearly Visitors: 129,598
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $31 USD
Yearly Revenue: $369 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: for.com 7
Domain Name: for 3
Extension (TLD): com 3

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 71
Performance 99
Accessibility 77
Best Practices 69
SEO 80
Progressive Web App 31
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
99

Performance

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

Metrics

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

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive for.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://for.com/
0
105.83500000212
266
0
301
text/html
http://www.for.com/
106.29700000572
234.47800000577
4088
6158
200
text/html
Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
246.94000000454
253.65000000602
30889
86927
200
text/javascript
Script
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
247.20500000694
367.99600000086
114052
314521
200
application/x-javascript
Script
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
286.042000007
372.07400000625
81646
81268
200
image/jpeg
Image
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
259.79600000574
278.5520000034
797
1296
200
application/x-javascript
Script
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
285.1820000069
316.14800000534
441
115
200
application/x-javascript
Script
http://www.google.com/adsense/domains/caf.js
285.41200000473
304.07400000695
58482
165397
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-1726084-83
286.29500000534
317.14300000021
34008
84729
200
application/javascript
Script
http://privacy.digimedia.com/check_cookie_country_code.js
285.76300000714
362.90200000076
5255
4775
200
application/javascript
Script
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
286.46600000502
304.84400000569
362
53
200
text/css
Stylesheet
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
286.85000000405
336.15700000519
769
1007
200
text/css
Stylesheet
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300169%2C17300171%2C17300194%2C17300196%2C17300200%2C17300203%2C17300205&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555089106&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=72&frm=0&uio=sl1sr1-&jsv=81863&rurl=http%3A%2F%2Fwww.for.com%2F
350.27500000433
411.87300000456
0
0
-1
Document
http://www.for.com/px.gif?ch=1&rn=8.746000524016564
352.35000000102
1194.7410000066
776
43
200
image/gif
Image
http://www.for.com/px.gif?ch=2&rn=8.746000524016564
352.61300000275
374.67800000013
776
43
200
image/gif
Image
https://www.google-analytics.com/analytics.js
372.78100000549
377.459000003
19103
45892
200
text/javascript
Script
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300169%2C17300171%2C17300194%2C17300196%2C17300200%2C17300203%2C17300205&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555089106&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=72&frm=0&uio=sl1sr1-&jsv=81863&rurl=http%3A%2F%2Fwww.for.com%2F
420.84900000191
490.80600000161
7576
9078
200
text/html
Document
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=1995309850&t=pageview&_s=1&dl=http%3A%2F%2Fwww.for.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=for.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=186752399&gjid=1986525206&cid=1096624352.1590555089&tid=UA-1726084-83&_gid=975160104.1590555089&_r=1&gtm=2ou5e1&z=1484819090
484.43800000678
488.28300000605
630
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j82&a=1995309850&t=event&_s=2&dl=http%3A%2F%2Fwww.for.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=for.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&ec=domain_name&ea=index&el=for.com&_u=IEBAAUAB~&jid=&gjid=&cid=1096624352.1590555089&tid=UA-1726084-83&_gid=975160104.1590555089&gtm=2ou5e1&z=1695174489
484.75500000495
487.8400000016
643
35
200
image/gif
Image
https://www.google.com/adsense/domains/caf.js
502.75800000236
521.10500000708
60366
165354
200
text/javascript
Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js
583.21800000704
587.33300000313
6154
12483
200
text/javascript
Script
http://www.for.com/px.gif?type=not_blocked&n=10.679023395514456
1853.458000005
1879.0020000015
776
43
200
image/gif
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)
262.916
6.348
284.379
28.048
312.439
22.007
347.437
30.621
380.994
5.527
387.268
11.73
400.766
8.135
420.11
24.11
444.53
24.586
477.839
31.659
517.254
7.219
557.051
25.996
586.829
15.745
615.205
108.314
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. For.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. For.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. For.com should consider minifying CSS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. For.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://privacy.digimedia.com/check_cookie_country_code.js
4775
3096
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 130 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. For.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://for.com/
0
http://www.for.com/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. For.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 418 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
114052
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81646
https://www.google.com/adsense/domains/caf.js
60366
http://www.google.com/adsense/domains/caf.js
58482
https://www.googletagmanager.com/gtag/js?id=UA-1726084-83
34008
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30889
https://www.google-analytics.com/analytics.js
19103
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300169%2C17300171%2C17300194%2C17300196%2C17300200%2C17300203%2C17300205&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555089106&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=72&frm=0&uio=sl1sr1-&jsv=81863&rurl=http%3A%2F%2Fwww.for.com%2F
7576
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js
6154
http://privacy.digimedia.com/check_cookie_country_code.js
5255
Uses efficient cache policy on static assets — 1 resource found
For.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
19103
Avoids an excessive DOM size — 49 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
49
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. For.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.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://www.google.com/adsense/domains/caf.js
146.828
132.641
6.252
Other
114.191
7.458
1.914
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
281.872
Other
52.033
Style & Layout
34.701
Script Parsing & Compilation
26.767
Rendering
13.482
Parse HTML & CSS
11.95
Garbage Collection
5.661
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 — 22 requests • 418 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
22
427855
Script
10
329547
Image
6
85247
Document
3
11664
Stylesheet
2
1131
Other
1
266
Media
0
0
Font
0
0
Third-party
11
223106
Minimize third-party usage — Third-party code blocked the main thread for 40 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 Size (Bytes) Main-Thread Blocking Time (Ms)
132578
43.037
34008
0
30889
0
20376
0

Budgets

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

Opportunities

Eliminate render-blocking resources — Potential savings of 260 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. For.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30889
230
Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. For.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
114052
55289
Efficiently encode images — Potential savings of 64 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81268
65526
Serve images in next-gen formats — Potential savings of 74 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81268
76238
77

Accessibility

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

Navigation

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

ARIA

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

Audio and video

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

Names and labels

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

Tables and lists

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

Best practices

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

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

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

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

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

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://for.com/
http://www.for.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
http://www.for.com/px.gif?ch=1&rn=8.746000524016564
http://www.for.com/px.gif?ch=2&rn=8.746000524016564
http://www.for.com/px.gif?type=not_blocked&n=10.679023395514456
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 191
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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
2
Medium
80

SEO

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

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.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

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

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.

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

Progressive Web App

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

Fast and reliable

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

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

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

Installable

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://for.com/
http://www.for.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
http://www.for.com/px.gif?ch=1&rn=8.746000524016564
http://www.for.com/px.gif?ch=2&rn=8.746000524016564
http://www.for.com/px.gif?type=not_blocked&n=10.679023395514456
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

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

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 66
Performance 87
Accessibility 77
Best Practices 69
SEO 67
Progressive Web App 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: http://www.for.com
Updated: 27th May, 2020

2.74 seconds
First Contentful Paint (FCP)
27%
52%
21%

0.48 seconds
First Input Delay (FID)
1%
86%
13%

Simulate loading on mobile
87

Performance

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

Metrics

First Contentful Paint — 2.2 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 2.4 s
The time taken for the page contents to be visibly populated.

Other

Estimated Input Latency — 60 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive for.com as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://for.com/
0
21.899999992456
240
0
301
text/html
http://www.for.com/
22.303999983706
133.74600000679
4081
6158
200
text/html
Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
149.19399999781
155.95300000859
30889
86927
200
text/javascript
Script
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
149.62300000479
217.02899999218
113991
314521
200
application/x-javascript
Script
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
190.01500000013
224.53999999561
81646
81268
200
image/jpeg
Image
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
163.38300000643
182.32200000784
797
1296
200
application/x-javascript
Script
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
188.88499998138
206.4899999823
441
115
200
application/x-javascript
Script
http://www.google.com/adsense/domains/caf.js
189.08399998327
211.22800000012
58627
165613
200
text/javascript
Script
https://www.googletagmanager.com/gtag/js?id=UA-1726084-83
190.49099998665
209.4329999818
34023
84715
200
application/javascript
Script
http://privacy.digimedia.com/check_cookie_country_code.js
189.35699999565
258.39199998882
5230
4775
200
application/javascript
Script
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
190.73000000208
225.20399998757
362
53
200
text/css
Stylesheet
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
191.0130000033
210.10199998273
769
1007
200
text/css
Stylesheet
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300179%2C17300194%2C17300196%2C17300207%2C17300209&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555097831&u_w=412&u_h=660&biw=980&bih=1569&psw=964&psh=299&frm=0&uio=sl1sr1-&jsv=36240&rurl=http%3A%2F%2Fwww.for.com%2F
266.72399998643
339.95599998161
0
0
-1
Document
http://www.for.com/px.gif?ch=1&rn=4.158752858000927
274.27900000475
298.46200000611
776
43
200
image/gif
Image
http://www.for.com/px.gif?ch=2&rn=4.158752858000927
274.82900000177
298.22799999965
776
43
200
image/gif
Image
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300179%2C17300194%2C17300196%2C17300207%2C17300209&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555097831&u_w=412&u_h=660&biw=980&bih=1569&psw=964&psh=299&frm=0&uio=sl1sr1-&jsv=36240&rurl=http%3A%2F%2Fwww.for.com%2F
349.2350000015
431.91799998749
7353
8812
200
text/html
Document
https://www.google-analytics.com/analytics.js
362.10900000879
368.11700000544
19103
45892
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=674866048&t=pageview&_s=1&dl=http%3A%2F%2Fwww.for.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=for.com&sd=24-bit&sr=412x660&vp=980x1569&je=0&_u=IEBAAUAB~&jid=1066345917&gjid=494378005&cid=736075652.1590555098&tid=UA-1726084-83&_gid=1140800238.1590555098&_r=1&gtm=2ou5e1&z=905817668
405.91299999505
411.90000000643
630
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j82&a=674866048&t=event&_s=2&dl=http%3A%2F%2Fwww.for.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=for.com&sd=24-bit&sr=412x660&vp=980x1569&je=0&ec=domain_name&ea=index&el=for.com&_u=IEBAAUAB~&jid=&gjid=&cid=736075652.1590555098&tid=UA-1726084-83&_gid=1140800238.1590555098&gtm=2ou5e1&z=438493736
406.23599998071
411.34099999908
643
35
200
image/gif
Image
https://www.google.com/adsense/domains/caf.js
444.72599998699
463.24799998547
60091
165597
200
text/javascript
Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js
524.0080000076
527.87399999215
6154
12483
200
text/javascript
Script
http://www.for.com/px.gif?type=not_blocked&n=8.83050237455286
774.58199998364
1094.4629999867
776
43
200
image/gif
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)
167.885
9.435
194.666
27.419
222.102
18.821
254.2
12.482
269.336
36.865
309.707
6.456
316.27
25.642
341.988
5.813
348.188
33.565
383.138
11.996
403.671
33.94
465.71
6.956
505.116
26.985
538.038
13.42
560.083
94.519
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. For.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. For.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. For.com should consider minifying CSS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. For.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Enable text compression — Potential savings of 3 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://privacy.digimedia.com/check_cookie_country_code.js
4775
3096
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 110 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. For.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://for.com/
0
http://www.for.com/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. For.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 417 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113991
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81646
https://www.google.com/adsense/domains/caf.js
60091
http://www.google.com/adsense/domains/caf.js
58627
https://www.googletagmanager.com/gtag/js?id=UA-1726084-83
34023
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30889
https://www.google-analytics.com/analytics.js
19103
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia_js&channel=digi-caf_pef%2Cdigimedia-template-15&adtest=false&psid=9039920606&kw=for&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300179%2C17300194%2C17300196%2C17300207%2C17300209&format=s&num=0&output=afd_ads&domain_name=www.for.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590555097831&u_w=412&u_h=660&biw=980&bih=1569&psw=964&psh=299&frm=0&uio=sl1sr1-&jsv=36240&rurl=http%3A%2F%2Fwww.for.com%2F
7353
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js
6154
http://privacy.digimedia.com/check_cookie_country_code.js
5230
Uses efficient cache policy on static assets — 1 resource found
For.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
19103
Avoids an excessive DOM size — 49 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
49
Maximum DOM Depth
12
Maximum Child Elements
16
Avoid chaining critical requests — 5 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. For.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 — 1.2 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://www.google.com/adsense/domains/caf.js
525.244
491.34
23.396
Other
492.188
37.972
9.204
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
211.348
169.484
23.024
https://www.google-analytics.com/analytics.js
132.932
127.436
5.496
http://www.for.com/
117.888
106.052
4.192
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
96.716
80.496
7.668
https://www.googletagmanager.com/gtag/js?id=UA-1726084-83
76.5
65.516
10.984
Minimizes main-thread work — 1.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
1114.252
Other
210.816
Style & Layout
168.552
Script Parsing & Compilation
108.976
Parse HTML & CSS
58.012
Rendering
54.128
Garbage Collection
1.856
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 — 22 requests • 417 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
22
427398
Script
10
329346
Image
6
85247
Document
3
11434
Stylesheet
2
1131
Other
1
240
Media
0
0
Font
0
0
Third-party
11
222743

Budgets

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

Metrics

First Meaningful Paint — 2.9 s
The time taken for the primary content of the page to be rendered.
Time to Interactive — 4.8 s
The time taken for the page to become fully interactive.
First CPU Idle — 4.3 s
The time taken for the page's main thread to be quiet enough to handle input.

Other

Total Blocking Time — 530 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).
First Contentful Paint (3G) — 4100 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. For.com should consider minifying JS files.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
113991
55260
Efficiently encode images — Potential savings of 64 KB
Unoptimized images can consume more cellular data than what is necessary.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81268
65526
Serve images in next-gen formats — Potential savings of 74 KB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Size (Bytes) Potential Savings (Bytes)
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
81268
76238

Metrics

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

Opportunities

Eliminate render-blocking resources — Potential savings of 890 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. For.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
30889
780

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 410 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 Size (Bytes) Main-Thread Blocking Time (Ms)
132225
310.076
20376
72.452
30889
27.324
34023
0
77

Accessibility

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

Navigation

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

ARIA

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

Audio and video

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

Names and labels

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

Tables and lists

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

Best practices

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

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

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

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

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Manual Checks

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

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
1.12.4
jQuery (Fast path)
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://for.com/
http://www.for.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
http://www.for.com/px.gif?ch=1&rn=4.158752858000927
http://www.for.com/px.gif?ch=2&rn=4.158752858000927
http://www.for.com/px.gif?type=not_blocked&n=8.83050237455286
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 190
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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
2
Medium
67

SEO

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

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.

Mobile Friendly

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

Content Best Practices

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

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

Progressive Web App

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

Fast and reliable

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

PWA Optimized

Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

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

Installable

Does not use HTTPS — 14 insecure requests found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://for.com/
http://www.for.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.for.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.for.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMTEvMzMvNzY4L3Rvbi5qcGciXSxbInAiLCJ0aHVtYiIsIjc1MHgyMDAjIl1d/ton.jpg
http://www.for.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.for.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.for.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.for.com/assets/belt_layout_caf-4a3dea87ed4a809b49d0640b48d26654.css
http://www.for.com/px.gif?ch=1&rn=4.158752858000927
http://www.for.com/px.gif?ch=2&rn=4.158752858000927
http://www.for.com/px.gif?type=not_blocked&n=8.83050237455286
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of for.com on mobile screens.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

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

Server Location

Server IP Address: 23.23.86.44
Continent: North America
Country: United States
United States Flag
Region: Virginia
City: Ashburn
Longitude: -77.4728
Latitude: 39.0481
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Amazon Data Services NoVa
Registration

Domain Registrant

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

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating: 0.1/5
WOT Trustworthiness: 1/100
WOT Child Safety: 1/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
for.com. 23.23.86.44 IN 599

NS Records

Host Nameserver Class TTL
for.com. ns2.digimedia.com. IN 599
for.com. ns1.digimedia.com. IN 599

MX Records

Priority Host Server Class TTL
1000 for.com. 0.0.0.0. IN 599

SOA Records

Domain Name Primary NS Responsible Email TTL
for.com. ns1.digimedia.com. dns.digimedia.com. 599

TXT Records

Host Value Class TTL
for.com. v=spf1 IN 599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 27th May, 2020
Content-Type: text/html; charset=utf-8
Server: nginx/1.10.1
Cache-Control: max-age=0, private, must-revalidate
Connection: keep-alive
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBAL/3/SrV7P8AsTHMFSpPmYbyv2PkACHwmG9Z+1IFZq3vA54IN7pQcGnhgNo+8SN9r/KtUWCb9OPqTfWM1N4w/EUCAwEAAQ==_NOkDTwqhNycQanvhV7A3UmGTrgLYPyaFFpnVeLPKg5iyHK9ebNiGQVlCsBon3DYwFyUV0P6ZfC9Ae8aa6/U2nw==
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: *
Access-Control-Request-Method: *
Access-Control-Allow-Headers: *
Access-Control-Max-Age: 86400
X-UA-Compatible: IE=Edge,chrome=1
ETag: "b60a47f215f4e21c3d745c4f00c9876b"
Set-Cookie: *
X-Request-Id: 7f560fcdb3f0c318a80dd76b3bd2d986
X-Runtime: 0.056909
X-Rack-Cache: miss

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns1.digimedia.com
ns2.digimedia.com
Full Whois: IP Address: 67.205.137.127
Maximum Daily connection limit reached. Lookup refused.

Nameservers

Name IP Address
ns1.digimedia.com 23.21.242.88
ns2.digimedia.com 23.21.243.119
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$1,091,759 USD 4/5
$1,049 USD 1/5
$6,905 USD 2/5
$197 USD
0/5

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

Domain Valuation Snoop Score
$2,641 USD 2/5
$978 USD 1/5
0/5
$1,048 USD 2/5
$3,656 USD 2/5