Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

jerrycan.co.uk

jerrycan.co.uk

Page Load Speed

3.5 sec in total

First Response

355 ms

Resources Loaded

2.6 sec

Page Rendered

571 ms

jerrycan.co.uk screenshot

About Website

Visit jerrycan.co.uk now to see the best up-to-date Jerrycan content and also check out these interesting facts you probably never knew about jerrycan.co.uk

Visit jerrycan.co.uk

Key Findings

We analyzed Jerrycan.co.uk page load time and found that the first response time was 355 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

jerrycan.co.uk performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

jerrycan.co.uk

355 ms

www.hartleige.com

260 ms

shop.css

175 ms

shop.js

180 ms

AC_RunActiveContent.js

149 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Jerrycan.co.uk, 93% (40 requests) were made to Hartleige.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Hartleige.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.6 kB (16%)

Content Size

665.0 kB

After Optimization

556.4 kB

In fact, the total size of Jerrycan.co.uk main page is 665.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 631.2 kB which makes up the majority of the site volume.

HTML Optimization

-30%

Potential reduce by 74 B

  • Original 243 B
  • After minification 242 B
  • After compression 169 B

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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 74 B or 30% of the original size.

Image Optimization

-15%

Potential reduce by 95.9 kB

  • Original 631.2 kB
  • After minification 535.3 kB

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. Obviously, Jerrycan needs image optimization as it can save up to 95.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-33%

Potential reduce by 9.8 kB

  • Original 29.9 kB
  • After minification 26.4 kB
  • After compression 20.1 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 9.8 kB or 33% of the original size.

CSS Optimization

-77%

Potential reduce by 2.8 kB

  • Original 3.7 kB
  • After minification 2.7 kB
  • After compression 829 B

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. Jerrycan.co.uk needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (55%)

Requests Now

42

After Optimization

19

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

Accessibility Review

jerrycan.co.uk accessibility score

33

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

jerrycan.co.uk best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

jerrycan.co.uk SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jerrycan.co.uk can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Jerrycan.co.uk main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Jerrycan. 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: