Tools & Wizards About Us
chrishardie.com screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

chrishardie.com

Chris Hardie - software developer, digital media producer, writer, entrepreneur

Page Load Speed

3.9 sec in total

First Response

96 ms

Resources Loaded

2.5 sec

Page Rendered

1.3 sec

chrishardie.com screenshot

About Website

Visit chrishardie.com now to see the best up-to-date Chris Hardie content for United States and also check out these interesting facts you probably never knew about chrishardie.com

Software developer and digital media consultant working on the intersections of journalism, technology, local news and civic engagement.

Visit chrishardie.com

Key Findings

We analyzed Chrishardie.com page load time and found that the first response time was 96 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

chrishardie.com performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

chrishardie.com

96 ms

chrishardie.com

803 ms

wp-emoji-release.min.js

151 ms

twentyfifteen.css

117 ms

orgSeries.css

116 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 66% of them (44 requests) were addressed to the original Chrishardie.com, 9% (6 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Secure.gravatar.com. The less responsive or slowest element that took the longest time to load (884 ms) belongs to the original domain Chrishardie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 517.9 kB (41%)

Content Size

1.3 MB

After Optimization

753.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chrishardie.com main page is 1.3 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 597.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 40.6 kB

  • Original 55.2 kB
  • After minification 53.4 kB
  • After compression 14.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 40.6 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 20.7 kB

  • Original 597.7 kB
  • After minification 577.0 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. Chris Hardie images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 259.1 kB

  • Original 373.6 kB
  • After minification 335.6 kB
  • After compression 114.5 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 259.1 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 197.6 kB

  • Original 245.2 kB
  • After minification 217.0 kB
  • After compression 47.6 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. Chrishardie.com needs all CSS files to be minified and compressed as it can save up to 197.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chrishardie.com

chrishardie.com

96 ms

chrishardie.com

chrishardie.com

803 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

151 ms

twentyfifteen.css

twentyfifteen.css

117 ms

orgSeries.css

orgSeries.css

116 ms

social_widget.css

social_widget.css

118 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

165 ms

wp-mediaelement.css

wp-mediaelement.css

137 ms

css

css

68 ms

genericons.css

genericons.css

255 ms

style.css

style.css

219 ms

twentyfifteen.css

twentyfifteen.css

232 ms

jetpack.css

jetpack.css

305 ms

jquery.js

jquery.js

357 ms

jquery-migrate.min.js

jquery-migrate.min.js

266 ms

fdfootnotes.js

fdfootnotes.js

320 ms

spin.js

spin.js

358 ms

jquery.spin.js

jquery.spin.js

364 ms

infinity.js

infinity.js

406 ms

jquery.cycle.js

jquery.cycle.js

468 ms

slideshow-shortcode.js

slideshow-shortcode.js

419 ms

devicepx-jetpack.js

devicepx-jetpack.js

31 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

553 ms

wp-mediaelement.js

wp-mediaelement.js

450 ms

gprofiles.js

gprofiles.js

158 ms

wpgroho.js

wpgroho.js

447 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

507 ms

functions.js

functions.js

521 ms

wp-embed.min.js

wp-embed.min.js

551 ms

e-201611.js

e-201611.js

35 ms

style.css

style.css

464 ms

ga.js

ga.js

82 ms

980444c18fd50bb6c9e4b05b453b1d7e.jpg

980444c18fd50bb6c9e4b05b453b1d7e.jpg

531 ms

18084451275_c3f09eb7cc_n.jpg

18084451275_c3f09eb7cc_n.jpg

521 ms

23502318303_c4931180a8.jpg

23502318303_c4931180a8.jpg

521 ms

twitter.png

twitter.png

386 ms

facebook.png

facebook.png

385 ms

googleplus.png

googleplus.png

469 ms

github.png

github.png

468 ms

linkedin.png

linkedin.png

474 ms

flickr.png

flickr.png

469 ms

youtube.png

youtube.png

524 ms

delicious.png

delicious.png

524 ms

rss.png

rss.png

604 ms

email.png

email.png

602 ms

rss.png

rss.png

597 ms

barcelona-team-e1457623475353-825x510.jpg

barcelona-team-e1457623475353-825x510.jpg

800 ms

WordCamp-Dayton-2016-Logo-235x300.png

WordCamp-Dayton-2016-Logo-235x300.png

723 ms

9676187081_804b8d7997_k-825x510.jpg

9676187081_804b8d7997_k-825x510.jpg

756 ms

80558500_2c68cac608_o-825x510.jpg

80558500_2c68cac608_o-825x510.jpg

822 ms

3549285383_11de3317a6_b-825x510.jpg

3549285383_11de3317a6_b-825x510.jpg

884 ms

fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf

fVu1p3782bqS2z-CaJvp9i3USBnSvpkopQaUR-2r7iU.ttf

390 ms

lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf

lJAvZoKA5NttpPc9yc6lPbOLyRJkM5aLlPlkJMOAyH0.ttf

413 ms

PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf

PIbvSEyHEdL91QLOQRnZ19qQynqKV_9Plp7mupa0S4g.ttf

424 ms

erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf

erE3KsIWUumgD1j_Ca-V-6CWcynf_cDxXwCLxiixG1c.ttf

424 ms

widgets.js

widgets.js

556 ms

Genericons.svg

Genericons.svg

774 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

31 ms

HQXBIwLHsOJCNEQeX9kNz9qQynqKV_9Plp7mupa0S4g.ttf

HQXBIwLHsOJCNEQeX9kNz9qQynqKV_9Plp7mupa0S4g.ttf

396 ms

Wreg0Be4tcFGM2t6VWytvKp5NA6AAOjfQM_HmvD0shQ.ttf

Wreg0Be4tcFGM2t6VWytvKp5NA6AAOjfQM_HmvD0shQ.ttf

396 ms

__utm.gif

__utm.gif

332 ms

hovercard.css

hovercard.css

89 ms

services.css

services.css

136 ms

g.gif

g.gif

79 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

30 ms

syndication

syndication

105 ms

563740808264687617

563740808264687617

179 ms

Accessibility Review

chrishardie.com accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Best Practices

chrishardie.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

chrishardie.com SEO score

91

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

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chrishardie.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 Chrishardie.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

chrishardie.com

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