Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

johnwhitaker.com

Horse Riding Breeches, Equine Rugs, Saddley, Bridlework and Tack | John Whitaker International

Page Load Speed

4.8 sec in total

First Response

198 ms

Resources Loaded

4 sec

Page Rendered

549 ms

johnwhitaker.com screenshot

About Website

Welcome to johnwhitaker.com homepage info - get ready to check John Whitaker best content right away, or after learning these important things about johnwhitaker.com

We are John Whitaker International Limited, market leaders in the manufacture and supply of the exclusive Whitaker Range of equestrian products. We take great pride in providing only the very finest p...

Visit johnwhitaker.com

Key Findings

We analyzed Johnwhitaker.com page load time and found that the first response time was 198 ms and then it took 4.6 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

johnwhitaker.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value1,200 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

johnwhitaker.com

198 ms

johnwhitaker.com

777 ms

bootstrap.css

100 ms

stylesheet.css

195 ms

font.css

286 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 79% of them (104 requests) were addressed to the original Johnwhitaker.com, 6% (8 requests) were made to Static.xx.fbcdn.net and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Johnwhitaker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.4 kB (7%)

Content Size

4.7 MB

After Optimization

4.4 MB

In fact, the total size of Johnwhitaker.com main page is 4.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. 75% 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 246.2 kB

  • Original 276.5 kB
  • After minification 227.0 kB
  • After compression 30.2 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 49.5 kB, which is 18% 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 246.2 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 61.7 kB

  • Original 4.1 MB
  • After minification 4.1 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. John Whitaker images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 11.9 kB

  • Original 228.8 kB
  • After minification 224.6 kB
  • After compression 216.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 6.5 kB

  • Original 52.2 kB
  • After minification 52.2 kB
  • After compression 45.7 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. Johnwhitaker.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (31%)

Requests Now

118

After Optimization

82

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

Accessibility Review

johnwhitaker.com accessibility score

75

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

johnwhitaker.com best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

johnwhitaker.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnwhitaker.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Johnwhitaker.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 John Whitaker. 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: