Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

stuartduff.com

Stuart Duff - Web Developer, Tea Drinker, Over Thinker

Page Load Speed

3.4 sec in total

First Response

240 ms

Resources Loaded

1.7 sec

Page Rendered

1.5 sec

stuartduff.com screenshot

About Website

Welcome to stuartduff.com homepage info - get ready to check Stuart Duff best content right away, or after learning these important things about stuartduff.com

Web Developer, Tea Drinker, Over Thinker

Visit stuartduff.com

Key Findings

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

stuartduff.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

stuartduff.com

240 ms

css

48 ms

a2b955aec87af70b896107f1805c44b6.css

15 ms

0b42c8bf9c046bf928209bb73f1a803b.css

22 ms

57d546dd7990c015ffe50945975d365e.css

20 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 39% of them (20 requests) were addressed to the original Stuartduff.com, 24% (12 requests) were made to Scontent.cdninstagram.com and 12% (6 requests) were made to Appicons.about.me. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Scontent.cdninstagram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.1 kB (6%)

Content Size

1.2 MB

After Optimization

1.1 MB

In fact, the total size of Stuartduff.com main page is 1.2 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 63.7 kB

  • Original 77.4 kB
  • After minification 77.2 kB
  • After compression 13.7 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. 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 63.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 9.3 kB

  • Original 1.1 MB
  • After minification 1.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. Stuart Duff images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 65 B

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

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 Stuart Duff. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

stuartduff.com accessibility score

91

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

stuartduff.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

stuartduff.com SEO score

97

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stuartduff.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stuartduff.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 data is detected on the main page of Stuart Duff. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: