Tools & Wizards About Us
jamesfuthey.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

jamesfuthey.com

James Futhey, Founder & Designer | Seattle & Taipei

Page Load Speed

554 ms in total

First Response

60 ms

Resources Loaded

416 ms

Page Rendered

78 ms

jamesfuthey.com screenshot

About Website

Click here to check amazing James Futhey content. Otherwise, check out these important facts you probably never knew about jamesfuthey.com

Visit jamesfuthey.com

Key Findings

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

jamesfuthey.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

jamesfuthey.com

60 ms

www.jamesfuthey.com

93 ms

pico.min.css

221 ms

basscss.min.css

225 ms

style.css

22 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 50% of them (6 requests) were addressed to the original Jamesfuthey.com, 25% (3 requests) were made to Cdnjs.cloudflare.com and 8% (1 request) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (225 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.6 kB (10%)

Content Size

34.9 kB

After Optimization

31.3 kB

  • HTML
  • Images

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

HTML Optimization

-72%

Potential reduce by 3.6 kB

  • Original 4.9 kB
  • After minification 3.7 kB
  • After compression 1.4 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 1.3 kB, which is 25% 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 3.6 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 29.9 kB
  • After minification 29.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. James Futhey images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 4 (44%)

Requests Now

9

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jamesfuthey.com

jamesfuthey.com

60 ms

www.jamesfuthey.com

www.jamesfuthey.com

93 ms

pico.min.css

pico.min.css

221 ms

basscss.min.css

basscss.min.css

225 ms

style.css

style.css

22 ms

pico-colors.css

pico-colors.css

68 ms

page-styles.css

page-styles.css

70 ms

Tc2qtfwP_400x400.jpg

Tc2qtfwP_400x400.jpg

33 ms

ionicons.js

ionicons.js

53 ms

a.js

a.js

148 ms

cash.min.js

cash.min.js

222 ms

editor.js

editor.js

75 ms

Accessibility Review

jamesfuthey.com accessibility score

54

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

jamesfuthey.com SEO score

83

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

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

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

jamesfuthey.com

Open Graph description is not detected on the main page of James Futhey. 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: