Tools & Wizards About Us
james-taylor.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

james-taylor.com

James Taylor Online – James Taylor's online home since 1994

Page Load Speed

1.7 sec in total

First Response

81 ms

Resources Loaded

1.5 sec

Page Rendered

165 ms

james-taylor.com screenshot

About Website

Click here to check amazing James Taylor content for United States. Otherwise, check out these important facts you probably never knew about james-taylor.com

Singer-songwriter James Taylor's unofficial online home since 1994 -- with frequently updated news, tour dates, discussion forums, and more.

Visit james-taylor.com

Key Findings

We analyzed James-taylor.com page load time and found that the first response time was 81 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

james-taylor.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value2,570 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value21.3 s

1/100

10%

Network Requests Diagram

james-taylor.com

81 ms

www.james-taylor.com

338 ms

style.min.css

57 ms

mediaelementplayer-legacy.min.css

84 ms

wp-mediaelement.min.css

92 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original James-taylor.com, 7% (3 requests) were made to Pagead2.googlesyndication.com and 4% (2 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

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

Content Size

809.0 kB

After Optimization

658.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 73.3 kB

  • Original 91.5 kB
  • After minification 87.3 kB
  • After compression 18.3 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 73.3 kB or 80% of the original size.

Image Optimization

-14%

Potential reduce by 67.5 kB

  • Original 492.8 kB
  • After minification 425.3 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. Obviously, James Taylor needs image optimization as it can save up to 67.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 5.9 kB

  • Original 128.1 kB
  • After minification 128.1 kB
  • After compression 122.2 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

-4%

Potential reduce by 3.9 kB

  • Original 96.6 kB
  • After minification 96.6 kB
  • After compression 92.7 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. James-taylor.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (78%)

Requests Now

41

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

james-taylor.com

james-taylor.com

81 ms

www.james-taylor.com

www.james-taylor.com

338 ms

style.min.css

style.min.css

57 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

84 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

92 ms

bbpress.min.css

bbpress.min.css

93 ms

ml-responsive-table.css

ml-responsive-table.css

96 ms

prettyPhoto.min.css

prettyPhoto.min.css

96 ms

style.css

style.css

98 ms

polls-css.css

polls-css.css

109 ms

fontawesome-all.min.css

fontawesome-all.min.css

119 ms

tc_common.min.css

tc_common.min.css

153 ms

red.min.css

red.min.css

126 ms

style.css

style.css

124 ms

jquery.fancybox-1.3.4.min.css

jquery.fancybox-1.3.4.min.css

124 ms

jetpack.css

jetpack.css

139 ms

jquery.min.js

jquery.min.js

177 ms

jquery-migrate.min.js

jquery-migrate.min.js

149 ms

ml.responsive.table.min.js

ml.responsive.table.min.js

149 ms

jquery.prettyPhoto.min.js

jquery.prettyPhoto.min.js

150 ms

underscore.min.js

underscore.min.js

166 ms

infinite-scroll.pkgd.min.js

infinite-scroll.pkgd.min.js

191 ms

front.js

front.js

176 ms

jquery.validate.js

jquery.validate.js

179 ms

jquery.fancybox-1.3.4.min.js

jquery.fancybox-1.3.4.min.js

175 ms

tc-scripts.min.js

tc-scripts.min.js

184 ms

js

js

84 ms

adsbygoogle.js

adsbygoogle.js

253 ms

adsbygoogle.js

adsbygoogle.js

553 ms

magic.js

magic.js

248 ms

qppr_frontend_script.min.js

qppr_frontend_script.min.js

249 ms

polls-js.js

polls-js.js

249 ms

core.min.js

core.min.js

250 ms

modernizr.min.js

modernizr.min.js

250 ms

OneSignalSDK.js

OneSignalSDK.js

50 ms

guitaricon-e1461894474641.png

guitaricon-e1461894474641.png

246 ms

AmericanStandard.png

AmericanStandard.png

383 ms

covers.jpg

covers.jpg

232 ms

BeforeThisWorld.jpg

BeforeThisWorld.jpg

231 ms

troubadour.jpg

troubadour.jpg

231 ms

busy.gif

busy.gif

231 ms

newsicon-e1463691068584.png

newsicon-e1463691068584.png

240 ms

show_ads_impl.js

show_ads_impl.js

345 ms

fa-solid-900.woff

fa-solid-900.woff

103 ms

fa-regular-400.woff

fa-regular-400.woff

75 ms

Accessibility Review

james-taylor.com accessibility score

98

Accessibility Issues

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

james-taylor.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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

james-taylor.com SEO score

90

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

    EN

  • Encoding

    UTF-8

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

james-taylor.com

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