High - High.com

Overview

Snoop Summary for high.com

This is a free and comprehensive report about high.com. High.com is hosted in Ashburn, Virginia in United States on a server with an IP address of 23.23.86.44, where the local currency is USD and English is the local language. If high.com was to be sold it would possibly be worth $738 USD (based on the daily revenue potential of the website over a 24 month period). High.com receives an estimated 350 unique visitors every day - a decent amount of traffic! This report was last updated 25th May, 2020.

About high.com

Site Preview:
Title:	High.com
Description:
Keywords and Tags:
Related Terms:
Fav Icon:
Age:	Over 26 years old
Domain Created:	20th May, 1997
Domain Updated:	25th January, 2018
Domain Expires:	21st May, 2027

Review

Snoop Score

1/5

Valuation

$738 USD

Note: All valuation figures are estimates.

Popularity

Low

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	3,764,418
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:	350
Monthly Visitors:	10,644
Yearly Visitors:	127,640

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$1 USD
Monthly Revenue:	$30 USD
Yearly Revenue:	$364 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	high.com	8
Domain Name:	high	4
Extension (TLD):	com	3

Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

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

Passing (40)
Average (1)

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.9 s
The time taken for the primary content of the page to be rendered.

Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.

Time to Interactive — 1.5 s
The time taken for the page to become fully interactive.

First CPU Idle — 1.1 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 80 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 high.com as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 60 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

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://high.com/	0	140.97199996468	267	0	301	text/html
http://www.high.com/	141.42499992158	297.31199995149	4483	7102	200	text/html	Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js	308.56199993286	314.4199999515	30889	86927	200	text/javascript	Script
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	308.81899991073	383.08399997186	113912	314521	200	application/x-javascript	Script
http://www.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg	309.0979999397	397.39499997813	19677	19292	200	image/jpeg	Image
http://www.high.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js	335.62199992593	385.43799996842	797	1296	200	application/x-javascript	Script
http://www.high.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js	335.7899999246	384.02899994981	441	115	200	application/x-javascript	Script
http://www.google.com/adsense/domains/caf.js	335.93199995812	353.96799992304	58479	165355	200	text/javascript	Script
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1	336.3829998998	356.62999993656	33840	84314	200	application/javascript	Script
http://privacy.digimedia.com/check_cookie_country_code.js	336.23499993701	413.49499998614	5255	4775	200	application/javascript	Script
http://www.high.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css	336.56699990388	366.49399995804	362	53	200	text/css	Stylesheet
http://www.high.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css	336.77699998952	385.14799997211	997	1761	200	text/css	Stylesheet
https://www.google.com/afs/ads/i/iframe.html	418.52399997879	423.4399999259	896	0	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	423.81599999499	429.81699993834	911	0	200	text/html	Document
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300169%2C17300171%2C17300191%2C17300193%2C17300203%2C17300205&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385261506&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=201&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	427.80999990646	489.59999997169	0	0	-1		Document
http://www.high.com/px.gif?ch=1&rn=10.102059501482765	431.59399996512	455.20699990448	776	43	200	image/gif	Image
http://www.high.com/px.gif?ch=2&rn=10.102059501482765	431.84899992775	1249.1019999143	776	43	200	image/gif	Image
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300169%2C17300171%2C17300191%2C17300193%2C17300203%2C17300205&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385261506&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=201&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	497.84499988891	596.00299992599	7723	9849	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	499.73399995361	504.99099993613	1680	1243	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	500.82600000314	506.76599994767	1593	1243	200	text/html	Document
https://www.google-analytics.com/analytics.js	515.82199998666	521.23299997766	19103	45892	200	text/javascript	Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=1083355638&t=pageview&_s=1&dl=http%3A%2F%2Fwww.high.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=high.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=896521607&gjid=1038417552&cid=218689586.1590385262&tid=UA-32054758-1&_gid=914597984.1590385262&_r=1&gtm=2ou5e1&z=964829658	563.00299998838	567.11199996062	630	35	200	image/gif	Image
https://www.google-analytics.com/collect?v=1&_v=j82&a=1083355638&t=event&_s=2&dl=http%3A%2F%2Fwww.high.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=high.com&sd=24-bit&sr=800x600&vp=1350x940&je=0&ec=domain_name&ea=index&el=high.com&_u=IEBAAUAB~&jid=&gjid=&cid=218689586.1590385262&tid=UA-32054758-1&_gid=914597984.1590385262&gtm=2ou5e1&z=1885877258	563.27599997167	566.42199994531	643	35	200	image/gif	Image
https://www.google.com/adsense/domains/caf.js	604.65100000147	622.5549998926	60047	165345	200	text/javascript	Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	697.98199995421	702.25799991749	6154	12483	200	text/javascript	Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	698.72399989981	703.26499990188	6154	12483	200	text/javascript	Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	702.78799999505	707.24799996242	6154	12483	200	text/javascript	Script
http://www.high.com/px.gif?type=not_blocked&n=5.672810722073033	1937.1819999069	2008.9649999281	776	43	200	image/gif	Image

Show Details

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)
326.451	6.811
346.495	17.753
417.594	42.168
462.957	5.388
468.439	5.271
473.776	5.338
479.225	19.924
499.428	29.353
533.005	11.748
546.218	5.693
551.989	5.463
568.103	22.534
658.445	48.223
713.178	10.138
733.947	5.205
742.484	78.921
821.446	68.775
890.27	69.77
962.958	21.736

Show Details

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. High.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. High.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. High.com should consider minifying CSS files.

Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. High.com should consider minifying JS files.

URL	Size (Bytes)	Potential Savings (Bytes)
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	113912	55221

Show Details

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. High.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 — Potential savings of 6 KB
Unoptimized images can consume more cellular data than what is necessary.

URL	Size (Bytes)	Potential Savings (Bytes)
http://www.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg	19292	6353

Show Details

Serve images in next-gen formats — Potential savings of 12 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.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg	19292	12016

Show Details

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

Show Details

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 160 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. High.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://high.com/	0
http://www.high.com/	190

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. High.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 373 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	113912
https://www.google.com/adsense/domains/caf.js	60047
http://www.google.com/adsense/domains/caf.js	58479
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1	33840
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js	30889
http://www.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg	19677
https://www.google-analytics.com/analytics.js	19103
https://www.google.com/dp/ads?adrep=3&r=m&cpp=0&client=dp-digimedia3_js&channel=digi-caf_pef%2Cdigimedia-template-04&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300169%2C17300171%2C17300191%2C17300193%2C17300203%2C17300205&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385261506&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=201&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w478h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	7723
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	6154
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	6154

Show Details

Uses efficient cache policy on static assets — 1 resource found
High.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

Show Details

Avoids an excessive DOM size — 54 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		54
Maximum DOM Depth	SHOW DETAILS	10
Maximum Child Elements	SHOW DETAILS	16

Show Details

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. High.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

URL	Total CPU Time (Ms)	Script Evaluation (Ms)	Script Parse (Ms)
https://www.google.com/adsense/domains/caf.js	274.717	254.003	7.524
Other	137.33	10.631	5.411

Show Details

Minimizes main-thread work — 0.6 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	395.401
Other	67.094
Script Parsing & Compilation	33.56
Garbage Collection	27.137
Style & Layout	24.484
Parse HTML & CSS	13.13
Rendering	9.609

Show Details

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 — 28 requests • 374 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	28	383415
Script	12	341225
Image	6	23278
Document	7	17286
Stylesheet	2	1359
Other	1	267
Media	0	0
Font	0	0
Third-party	17	240151

Show Details

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)
SHOW DETAILS	149791	41.985
SHOW DETAILS	33840	0
SHOW DETAILS	30889	0
SHOW DETAILS	20376	0

Show Details

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 250 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. High.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

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of high.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"]`
High.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
High.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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

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

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Names and labels

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

Show Details

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
html

Show Details

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.

Best Practices

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

Passing (10)
Failing (4)

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)

Show Details

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://high.com/
http://www.high.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg
http://www.high.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.high.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.high.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.high.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css
http://www.high.com/px.gif?ch=1&rn=10.102059501482765
http://www.high.com/px.gif?ch=2&rn=10.102059501482765
http://www.high.com/px.gif?type=not_blocked&n=5.672810722073033

Show Details

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

Show Details

Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

URL	Target	Rel
http://www.motels.com/	_blank

Show Details

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
SHOW DETAILS	2	Medium

Show Details

SEO

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

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 high.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://high.com/
http://www.high.com/
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js
http://www.high.com/media/W1siZiIsIjIwMTIvMDQvMjYvMjAvMDcvMjAvNjgwL2RpYWx1cC5jb20uanBnIl0sWyJwIiwidGh1bWIiLCIyNTB4MjAwIyJdXQ/dialup.com.jpg
http://www.high.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js
http://www.high.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js
http://www.google.com/adsense/domains/caf.js
http://privacy.digimedia.com/check_cookie_country_code.js
http://www.high.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css
http://www.high.com/assets/google_caf_reflex-2b4f1e055ab27b739ad375f09d99be17.css
http://www.high.com/px.gif?ch=1&rn=10.102059501482765
http://www.high.com/px.gif?ch=2&rn=10.102059501482765
http://www.high.com/px.gif?type=not_blocked&n=5.672810722073033

Show Details

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

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

URL: http://www.high.com

Updated: 25th May, 2020

3.22 seconds

First Contentful Paint (FCP)

30%

42%

28%

0.30 seconds

First Input Delay (FID)

76%

20%

4%

Simulate loading on mobile

Performance

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

Metrics

Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.

Opportunities

Properly size images
Images can slow down the page's load time. High.com should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. High.com should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. High.com should consider minifying CSS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. High.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression — 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

Show Details

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 90 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. High.com should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
(Start) http://high.com/	0
http://www.high.com/	630

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. High.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 354 KB
Large network payloads can cost users money and are linked to long load times.

URL	Size (Bytes)
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	113936
https://www.google.com/adsense/domains/caf.js	60407
http://www.google.com/adsense/domains/caf.js	58468
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1	33840
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-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300194%2C17300196&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385271348&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	7701
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	6154
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	6154
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	6154

Show Details

Uses efficient cache policy on static assets — 1 resource found
High.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

Show Details

Avoids an excessive DOM size — 50 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		50
Maximum DOM Depth	SHOW DETAILS	10
Maximum Child Elements	SHOW DETAILS	16

Show Details

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

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 — 28 requests • 356 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	28	364469
Script	12	341592
Document	7	17310
Image	6	4379
Stylesheet	2	936
Other	1	252
Media	0	0
Font	0	0
Third-party	18	241425

Show Details

Budgets

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

Other

Network Requests
Below is a list of network requests that were made during page load.

URL	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://high.com/	0	31.400999985635	252	0	301	text/html
http://www.high.com/	31.827999977395	116.57100007869	4354	6870	200	text/html	Document
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js	128.42800002545	135.15400001779	30889	86927	200	text/javascript	Script
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	128.57599998824	168.21700008586	113936	314521	200	application/x-javascript	Script
http://www.high.com/assets/abp2-4831d5b24977f8140fd9aa25543527f2.js	128.70700005442	145.39299998432	797	1296	200	application/x-javascript	Script
http://www.high.com/assets/ads-832e97bfd2d3e735f6dc8a30dd7190bc.js	129.03499999084	145.78999998048	441	115	200	application/x-javascript	Script
http://www.google.com/adsense/domains/caf.js	129.37500001863	146.48999995552	58468	165345	200	text/javascript	Script
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1	129.60799993016	153.80099997856	33840	84314	200	application/javascript	Script
http://privacy.digimedia.com/check_cookie_country_code.js	129.68900008127	164.29500002414	5249	4775	200	application/javascript	Script
http://www.high.com/assets/style-85cdb3be1709c9028b204b38f8ccb358.css	165.40100006387	181.65499996394	362	53	200	text/css	Stylesheet
http://www.high.com/assets/mobile-7b7fa1a9a2489ff075167a8fa764dd14.css	165.5449999962	182.74400010705	574	263	200	text/css	Stylesheet
https://www.google.com/afs/ads/i/iframe.html	205.97200002521	211.33899991401	896	0	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	211.63400006481	218.55700016022	911	0	200	text/html	Document
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300194%2C17300196&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385271348&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	215.66099999472	255.04399999045	0	0	-1		Document
http://www.high.com/px.gif?ch=1&rn=6.094743289760828	220.63599992543	242.49699991196	776	43	200	image/gif	Image
http://www.high.com/px.gif?ch=2&rn=6.094743289760828	221.64599993266	243.85700002313	776	43	200	image/gif	Image
https://www.google.com/dp/ads?adrep=3&r=m&client=dp-digimedia3_js&channel=afsonly%2Cdigimedia-template-12&adtest=false&psid=9039920606&kw=High%20School&terms=High%20School%2CHigh%20Speed%20Internet%2CHigh%20Blood%20Pressure%2CHigh%20Cholesterol%2CHigh%20Protein%20Diet&swp=as-drid-oo-1626960400946279&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300002%2C17300165%2C17300167%2C17300194%2C17300196&format=s%7Cs%7Cr5&num=0&output=afd_ads&domain_name=www.high.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1590385271348&u_w=412&u_h=660&biw=412&bih=660&psw=396&psh=104&frm=0&uio=sl1sr1---st18&cont=gencats&csize=w396h0&inames=slave-2-1&jsv=81863&rurl=http%3A%2F%2Fwww.high.com%2F	262.95000012033	356.40599997714	7701	9892	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	266.18800009601	271.39399992302	1765	1243	200	text/html	Document
https://www.google.com/afs/ads/i/iframe.html	266.72700000927	270.99000010639	1683	1243	200	text/html	Document
https://www.google-analytics.com/analytics.js	309.68599999323	313.99799999781	19103	45892	200	text/javascript	Script
https://www.google-analytics.com/r/collect?v=1&_v=j82&a=1980055520&t=pageview&_s=1&dl=http%3A%2F%2Fwww.high.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=high.com&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=583003580&gjid=335298702&cid=101172771.1590385271&tid=UA-32054758-1&_gid=7682910.1590385271&_r=1&gtm=2ou5e1&z=1992021162	363.1770000793	371.65999994613	630	35	200	image/gif	Image
https://www.google-analytics.com/collect?v=1&_v=j82&a=1980055520&t=event&_s=2&dl=http%3A%2F%2Fwww.high.com%2F&dp=%2F&ul=en-us&de=UTF-8&dt=high.com&sd=24-bit&sr=412x660&vp=412x660&je=0&ec=domain_name&ea=index&el=high.com&_u=IEBAAUAB~&jid=&gjid=&cid=101172771.1590385271&tid=UA-32054758-1&_gid=7682910.1590385271&gtm=2ou5e1&z=245493260	363.3550000377	366.58599996008	643	35	200	image/gif	Image
https://www.google.com/adsense/domains/caf.js	374.16799995117	391.53499994427	60407	165336	200	text/javascript	Script
https://www.gstatic.com/domainads/images/chevron-white.png	442.7920000162	446.19500008412	778	189	200	image/png	Image
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	468.88300008141	472.27500006557	6154	12483	200	text/javascript	Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	469.52400007285	473.43600005843	6154	12483	200	text/javascript	Script
https://www.google.com/js/bg/uUYt-IDfvvLFIpwwv3adQJJEKMythTQ2IYq8dchzXEY.js	472.90699998848	476.1179999914	6154	12483	200	text/javascript	Script
http://www.high.com/px.gif?type=not_blocked&n=3.5193333873356787	742.06899991259	1246.2559998967	776	43	200	image/gif	Image

Show Details

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)
142.95	6.107
165.367	25.287
193.115	11.654
208.374	40.907
256.805	7.399
269.108	19.968
290.305	21.303
311.857	10.128
326.104	9.547
341.307	5.287
362.014	25.986
388.925	5.505
424.855	48.693
475.29	6.426
482.673	9.688
505.06	81.815
586.926	64.293
651.264	79.868
731.161	5.486
738.729	23.687

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Metrics

First Contentful Paint — 2.6 s
The time taken for the first image or text on the page to be rendered.

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

Time to Interactive — 5.6 s
The time taken for the page to become fully interactive.

First CPU Idle — 4.7 s
The time taken for the page's main thread to be quiet enough to handle input.

Opportunities

Eliminate render-blocking resources — Potential savings of 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. High.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	1080

Show Details

Minify JavaScript — Potential savings of 54 KB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. High.com should consider minifying JS files.

URL	Size (Bytes)	Potential Savings (Bytes)
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	113936	55233

Show Details

Diagnostics

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)
https://www.google.com/adsense/domains/caf.js	1119.56	1019.624	29.284
Other	604.072	37.852	14.716
http://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js	174.748	154.544	11.796
http://www.high.com/	129.96	116.58	4.904
https://www.google-analytics.com/analytics.js	102.132	97.036	5.096
http://www.high.com/assets/application-ea87d7f1cf81efea754ac69b6a6922a8.js	98.148	69.44	24.308
https://www.googletagmanager.com/gtag/js?id=UA-32054758-1	59.596	49.224	10.372

Show Details

Minimize main-thread work — 2.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	1601.448
Other	284.18
Garbage Collection	146.82
Style & Layout	134.88
Script Parsing & Compilation	128.92
Parse HTML & CSS	46.424
Rendering	37.34

Show Details

Other

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

Metrics

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

Other

Estimated Input Latency — 130 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 high.com as laggy when the latency is higher than 0.05 seconds.

Total Blocking Time — 970 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).

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 800 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)
SHOW DETAILS	150293	703.576
SHOW DETAILS	31667	49.768
SHOW DETAILS	20376	43.52
SHOW DETAILS	33840	0

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of high.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"]`
High.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.

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

`<video>` elements contain a `<track>` element with `[kind="description"]`
High.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.

Contrast

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

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Internationalization and localization

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

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Names and labels

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

Show Details

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
html