Tools & Wizards About Us

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

williamwilkinson.com

William Wilkinson

Page Load Speed

2.2 sec in total

First Response

291 ms

Resources Loaded

855 ms

Page Rendered

1 sec

About Website

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

A designer from Victoria, BC. I make the iPhone apps Manual, Slide and Everyday. You can email me. Twitter • Facebook • Instagram • Archive • Ask

Visit williamwilkinson.com

Key Findings

We analyzed Williamwilkinson.com page load time and found that the first response time was 291 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster. This domain responded with an error, which can significantly jeopardize Williamwilkinson.com rating and web reputation

Performance Metrics

williamwilkinson.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value1,540 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.078

94/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

williamwilkinson.com

291 ms

pre_tumblelog.js

9 ms

reset.2.8.1.yui.css

15 ms

tumblelog_post_message_queue.js

15 ms

stylesheet.css

21 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Williamwilkinson.com, 26% (9 requests) were made to Assets.tumblr.com and 17% (6 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (538 ms) relates to the external source 40.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 832.7 kB (19%)

Content Size

4.4 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 30.2 kB

  • Original 39.3 kB
  • After minification 31.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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.2 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 104.1 kB

  • Original 3.3 MB
  • After minification 3.2 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. William Wilkinson images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 493.8 kB

  • Original 753.5 kB
  • After minification 752.9 kB
  • After compression 259.7 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 493.8 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 204.5 kB

  • Original 246.7 kB
  • After minification 245.6 kB
  • After compression 42.1 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. Williamwilkinson.com needs all CSS files to be minified and compressed as it can save up to 204.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (39%)

Requests Now

31

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

williamwilkinson.com accessibility score

52

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

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

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

williamwilkinson.com SEO score

89

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

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