Tools & Wizards About Us
williamjames.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

williamjames.com

New Thinking Allowed with Jeffrey Mishlove - YouTube

Page Load Speed

6.5 sec in total

First Response

407 ms

Resources Loaded

6 sec

Page Rendered

72 ms

williamjames.com screenshot

About Website

Click here to check amazing Williamjames content. Otherwise, check out these important facts you probably never knew about williamjames.com

This channel features content about philosophy, psychology, health, science, and spirituality -- with an emphasis on parapsychology. Host, Jeffrey Mishlove, ...

Visit williamjames.com

Key Findings

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

Performance Metrics

williamjames.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value15,600 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value26.9 s

0/100

10%

Network Requests Diagram

williamjames.com

407 ms

newthinkingallowed.com

268 ms

NewThinkingAllowed

779 ms

web-animations-next-lite.min.js

45 ms

webcomponents-all-noPatch.js

61 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Williamjames.com, 61% (14 requests) were made to Youtube.com and 17% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Accounts.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (89%)

Content Size

1.4 MB

After Optimization

152.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Williamjames.com main page is 1.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. 20% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 1.1 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 108.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. 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 1.1 MB or 91% of the original size.

JavaScript Optimization

-67%

Potential reduce by 87.7 kB

  • Original 131.3 kB
  • After minification 130.3 kB
  • After compression 43.6 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 87.7 kB or 67% of the original size.

CSS Optimization

-77%

Potential reduce by 4.5 kB

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 1.4 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. Williamjames.com needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 77% of the original size.

Requests Breakdown

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

Requests Now

14

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

williamjames.com

williamjames.com

407 ms

newthinkingallowed.com

newthinkingallowed.com

268 ms

NewThinkingAllowed

NewThinkingAllowed

779 ms

web-animations-next-lite.min.js

web-animations-next-lite.min.js

45 ms

webcomponents-all-noPatch.js

webcomponents-all-noPatch.js

61 ms

fetch-polyfill.js

fetch-polyfill.js

39 ms

intersection-observer.min.js

intersection-observer.min.js

39 ms

scheduler.js

scheduler.js

78 ms

www-i18n-constants.js

www-i18n-constants.js

40 ms

www-tampering.js

www-tampering.js

68 ms

spf.js

spf.js

68 ms

network.js

network.js

67 ms

css2

css2

91 ms

www-onepick.css

www-onepick.css

66 ms

rs=AGKMywFIYKx9Q-GRblgodFNyS5OH4a7r0Q

rs=AGKMywFIYKx9Q-GRblgodFNyS5OH4a7r0Q

70 ms

desktop_polymer_legacy_browsers.js

desktop_polymer_legacy_browsers.js

122 ms

ServiceLogin

ServiceLogin

5066 ms

www-main-desktop-watch-page-skeleton.css

www-main-desktop-watch-page-skeleton.css

5 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

116 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

133 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

162 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

183 ms

identifier

identifier

40 ms

Accessibility Review

williamjames.com accessibility score

87

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

williamjames.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

williamjames.com SEO score

92

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Williamjames.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 Williamjames.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

williamjames.com

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