Tools & Wizards About Us
chrisdrake.net screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

chrisdrake.net

Captcha

Page Load Speed

8.3 sec in total

First Response

109 ms

Resources Loaded

7.9 sec

Page Rendered

362 ms

chrisdrake.net screenshot

About Website

Click here to check amazing Chrisdrake content. Otherwise, check out these important facts you probably never knew about chrisdrake.net

Experienced full-stack web developer with a particular interest in WordPress and it’s many, many uses. Based in Creston, British Columbia.

Visit chrisdrake.net

Key Findings

We analyzed Chrisdrake.net page load time and found that the first response time was 109 ms and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

chrisdrake.net performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.188

65/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

chrisdrake.ca

109 ms

wp-emoji-release.min.js

25 ms

style.min.css

52 ms

classic-themes.min.css

58 ms

styles.css

58 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Chrisdrake.net, 12% (5 requests) were made to Fonts.gstatic.com and 10% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (189 ms) relates to the external source Use.fontawesome.com.

Page Optimization Overview & Recommendations

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

Content Size

925.8 kB

After Optimization

870.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chrisdrake.net main page is 925.8 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. 45% of websites need less resources to load. Images take 508.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.4 kB

  • Original 36.4 kB
  • After minification 33.9 kB
  • After compression 9.0 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 27.4 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 19.3 kB

  • Original 508.2 kB
  • After minification 488.9 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. Chrisdrake images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.7 kB

  • Original 347.5 kB
  • After minification 347.5 kB
  • After compression 341.8 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

-9%

Potential reduce by 2.9 kB

  • Original 33.6 kB
  • After minification 33.6 kB
  • After compression 30.8 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. Chrisdrake.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

33

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chrisdrake.ca

chrisdrake.ca

109 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

25 ms

style.min.css

style.min.css

52 ms

classic-themes.min.css

classic-themes.min.css

58 ms

styles.css

styles.css

58 ms

style.css

style.css

60 ms

all.css

all.css

129 ms

css

css

42 ms

picturefill.min.js

picturefill.min.js

57 ms

jquery.min.js

jquery.min.js

84 ms

jquery-migrate.min.js

jquery-migrate.min.js

66 ms

js

js

82 ms

index.js

index.js

70 ms

index.js

index.js

69 ms

gtm4wp-contact-form-7-tracker.js

gtm4wp-contact-form-7-tracker.js

72 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

71 ms

navigation.js

navigation.js

80 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

84 ms

js.js

js.js

83 ms

viewport-units-buggyfill.js

viewport-units-buggyfill.js

86 ms

wpcf7-recaptcha-controls.js

wpcf7-recaptcha-controls.js

86 ms

api.js

api.js

55 ms

gtm.js

gtm.js

108 ms

loader.svg

loader.svg

67 ms

recaptcha__en.js

recaptcha__en.js

115 ms

fly.png

fly.png

26 ms

googly-eyeballs.png

googly-eyeballs.png

45 ms

Christmas-Day-2014-1920x1080.jpg

Christmas-Day-2014-1920x1080.jpg

124 ms

Experience-Balfour-Featured-Image.jpg

Experience-Balfour-Featured-Image.jpg

138 ms

feet.jpg

feet.jpg

45 ms

googly-head.png

googly-head.png

72 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

27 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

36 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

44 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

48 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

49 ms

fa-solid-900.woff

fa-solid-900.woff

122 ms

fa-regular-400.woff

fa-regular-400.woff

158 ms

fa-brands-400.woff

fa-brands-400.woff

189 ms

analytics.js

analytics.js

62 ms

collect

collect

16 ms

js

js

41 ms

Accessibility Review

chrisdrake.net accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

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

chrisdrake.net 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

chrisdrake.net SEO score

100

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

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 Chrisdrake.net 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 Chrisdrake.net 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

chrisdrake.net

Open Graph data is detected on the main page of Chrisdrake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: