Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

head.com

Sports – HEAD

Page Load Speed

5 sec in total

First Response

294 ms

Resources Loaded

3.8 sec

Page Rendered

875 ms

head.com screenshot

About Website

Click here to check amazing HEAD content for United States. Otherwise, check out these important facts you probably never knew about head.com

Visit head.com

Key Findings

We analyzed Head.com page load time and found that the first response time was 294 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

head.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

head.com

294 ms

198 ms

cookieconsent.min.js

7 ms

stylesheet_459a08cb9c.css

182 ms

CssDemo.css

189 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 66% of them (102 requests) were addressed to the original Head.com, 5% (8 requests) were made to Head.com.cgi-labs.de and 5% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (42%)

Content Size

7.7 MB

After Optimization

4.5 MB

In fact, the total size of Head.com main page is 7.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 192.3 kB

  • Original 215.5 kB
  • After minification 145.4 kB
  • After compression 23.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 70.0 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 192.3 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 170.9 kB

  • Original 4.1 MB
  • After minification 3.9 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. HEAD images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.2 MB
  • After compression 352.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.3 MB or 79% of the original size.

CSS Optimization

-88%

Potential reduce by 1.5 MB

  • Original 1.7 MB
  • After minification 1.3 MB
  • After compression 200.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Head.com needs all CSS files to be minified and compressed as it can save up to 1.5 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (33%)

Requests Now

141

After Optimization

94

The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HEAD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

head.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

head.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

head.com SEO score

71

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    US

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Head.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Head.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of HEAD. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: