Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

peterwknox.com

Peter W. Knox

Page Load Speed

3.8 sec in total

First Response

386 ms

Resources Loaded

1.7 sec

Page Rendered

1.7 sec

peterwknox.com screenshot

About Website

Welcome to peterwknox.com homepage info - get ready to check Peter W Knox best content right away, or after learning these important things about peterwknox.com

Just a man and his blog, a place for all things Peter Knox on the internet.

Visit peterwknox.com

Key Findings

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

peterwknox.com performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value20.6 s

0/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value2,410 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.216

58/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

www.peterwknox.com

386 ms

pre_tumblelog.js

44 ms

index.build.css

53 ms

urchin.js

58 ms

bilmur.min.js

81 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Peterwknox.com, 38% (33 requests) were made to 64.media.tumblr.com and 14% (12 requests) were made to Images.gr-assets.com. The less responsive or slowest element that took the longest time to load (974 ms) relates to the external source Goodreads.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.2 kB (20%)

Content Size

602.2 kB

After Optimization

480.0 kB

In fact, the total size of Peterwknox.com main page is 602.2 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. 55% of websites need less resources to load. Images take 433.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 120.8 kB

  • Original 155.4 kB
  • After minification 152.7 kB
  • After compression 34.6 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 120.8 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 7 B

  • Original 433.9 kB
  • After minification 433.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. Peter W Knox images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 977 B

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

CSS Optimization

-13%

Potential reduce by 393 B

  • Original 2.9 kB
  • After minification 2.9 kB
  • After compression 2.5 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. Peterwknox.com needs all CSS files to be minified and compressed as it can save up to 393 B or 13% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

65

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

Accessibility Review

peterwknox.com accessibility score

43

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.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

peterwknox.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

peterwknox.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Peterwknox.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 Peterwknox.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 Peter W Knox. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: