Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

garymacdonald.com

garymacdonald.com

Page Load Speed

800 ms in total

First Response

156 ms

Resources Loaded

560 ms

Page Rendered

84 ms

garymacdonald.com screenshot

About Website

Visit garymacdonald.com now to see the best up-to-date Garymacdonald content and also check out these interesting facts you probably never knew about garymacdonald.com

Visit garymacdonald.com

Key Findings

We analyzed Garymacdonald.com page load time and found that the first response time was 156 ms and then it took 644 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

garymacdonald.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.7 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.7 s

100/100

25%

SI (Speed Index)

Value0.7 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.7 s

100/100

10%

Network Requests Diagram

garymacdonald.com

156 ms

css

25 ms

genericons.css

235 ms

style.css

179 ms

jetpack.css

194 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 7% of them (1 request) were addressed to the original Garymacdonald.com, 50% (7 requests) were made to Garymacdonaldcom.ipage.com and 29% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (235 ms) relates to the external source Garymacdonaldcom.ipage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.3 kB (72%)

Content Size

273.1 kB

After Optimization

75.8 kB

In fact, the total size of Garymacdonald.com main page is 273.1 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. 35% of websites need less resources to load. CSS take 158.3 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.1 kB

  • Original 8.3 kB
  • After minification 7.5 kB
  • After compression 2.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. 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 6.1 kB or 74% of the original size.

JavaScript Optimization

-65%

Potential reduce by 69.1 kB

  • Original 106.5 kB
  • After minification 105.0 kB
  • After compression 37.4 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 69.1 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 122.1 kB

  • Original 158.3 kB
  • After minification 139.6 kB
  • After compression 36.3 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. Garymacdonald.com needs all CSS files to be minified and compressed as it can save up to 122.1 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (38%)

Requests Now

8

After Optimization

5

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

Accessibility Review

garymacdonald.com accessibility score

71

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

Document doesn't have a <title> element

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

garymacdonald.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

garymacdonald.com SEO score

58

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Garymacdonald.com 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), while the claimed language is English. Our system also found out that Garymacdonald.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 Garymacdonald. 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: