Tools & Wizards About Us
whoisredjohn.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

whoisredjohn.com

Who is Red John - The latest theories about Red John's identity

Page Load Speed

2.7 sec in total

First Response

246 ms

Resources Loaded

2.1 sec

Page Rendered

319 ms

whoisredjohn.com screenshot

About Website

Click here to check amazing Who Is Red John content for United States. Otherwise, check out these important facts you probably never knew about whoisredjohn.com

Find all the informations about Red John, Mentalist's mysterious serial killer, read and share your theories, and much more...

Visit whoisredjohn.com

Key Findings

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

Performance Metrics

whoisredjohn.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value3,030 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

whoisredjohn.com

246 ms

www.whoisredjohn.com

559 ms

design.css

80 ms

adsbygoogle.js

174 ms

logo.png

158 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 31% of them (22 requests) were addressed to the original Whoisredjohn.com, 11% (8 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (559 ms) belongs to the original domain Whoisredjohn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.1 kB (29%)

Content Size

1.0 MB

After Optimization

721.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoisredjohn.com main page is 1.0 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. Javascripts take 664.2 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 43.6 kB

  • Original 56.0 kB
  • After minification 52.5 kB
  • After compression 12.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. 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 43.6 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 20.2 kB

  • Original 271.9 kB
  • After minification 251.7 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. Who Is Red John images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 210.8 kB

  • Original 664.2 kB
  • After minification 662.7 kB
  • After compression 453.3 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 210.8 kB or 32% of the original size.

CSS Optimization

-79%

Potential reduce by 14.4 kB

  • Original 18.2 kB
  • After minification 14.0 kB
  • After compression 3.8 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. Whoisredjohn.com needs all CSS files to be minified and compressed as it can save up to 14.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (49%)

Requests Now

61

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoisredjohn.com

whoisredjohn.com

246 ms

www.whoisredjohn.com

www.whoisredjohn.com

559 ms

design.css

design.css

80 ms

adsbygoogle.js

adsbygoogle.js

174 ms

logo.png

logo.png

158 ms

thomas_mcallister_small.png

thomas_mcallister_small.png

288 ms

reede_smith_small.png

reede_smith_small.png

316 ms

ray_haffner_small.png

ray_haffner_small.png

318 ms

gale_bertram_small.png

gale_bertram_small.png

318 ms

brett_partridge_small.png

brett_partridge_small.png

318 ms

bret_stiles_small.png

bret_stiles_small.png

319 ms

bob_kirkland_small.png

bob_kirkland_small.png

315 ms

jquery.min.js

jquery.min.js

42 ms

plugins.js

plugins.js

551 ms

main.js

main.js

393 ms

js

js

116 ms

count.js

count.js

37 ms

sdk.js

sdk.js

40 ms

widgets.js

widgets.js

31 ms

btn_donate_LG.gif

btn_donate_LG.gif

26 ms

bg-top.png

bg-top.png

284 ms

search_box_icon.png

search_box_icon.png

282 ms

summer_edgecombe_small.png

summer_edgecombe_small.png

284 ms

unrevealed_small.png

unrevealed_small.png

283 ms

patrick_jane_small.png

patrick_jane_small.png

360 ms

teresa_lisbon_small.png

teresa_lisbon_small.png

360 ms

footer-logo.png

footer-logo.png

360 ms

footer-website-name.png

footer-website-name.png

361 ms

sprites-footer-social.png

sprites-footer-social.png

362 ms

pixel.gif

pixel.gif

10 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

172 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

173 ms

show_ads_impl.js

show_ads_impl.js

248 ms

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

xjAJXh38I15wypJXxuGMBobN6UDyHWBl620a-IRfuBk.woff

11 ms

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

PRmiXeptR36kaC0GEAetxn5HxGBcBvicCpTp6spHfNo.woff

11 ms

zrt_lookup.html

zrt_lookup.html

23 ms

ads

ads

395 ms

count-data.js

count-data.js

70 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

25 ms

settings

settings

67 ms

sdk.js

sdk.js

9 ms

ads

ads

132 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

50 ms

embeds

embeds

56 ms

embeds

embeds

76 ms

embeds

embeds

77 ms

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

follow_button.2f70fb173b9000da126c79afe2098f02.en.html

12 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

41 ms

gen_204

gen_204

189 ms

pixel

pixel

188 ms

8244215060555915753

8244215060555915753

38 ms

abg_lite.js

abg_lite.js

22 ms

omrhp.js

omrhp.js

30 ms

40 ms

Q12zgMmT.js

Q12zgMmT.js

33 ms

window_focus.js

window_focus.js

39 ms

qs_click_protection.js

qs_click_protection.js

42 ms

ufs_web_display.js

ufs_web_display.js

28 ms

icon.png

icon.png

20 ms

62bHydCX.html

62bHydCX.html

135 ms

activeview

activeview

75 ms

pixel

pixel

91 ms

pixel

pixel

89 ms

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

wJiNEMIFAPB28UFvxM_UYtYFK_ILnv1_rxRzUTsn-Pg.js

9 ms

rum

rum

26 ms

pixel

pixel

25 ms

bounce

bounce

22 ms

rum

rum

24 ms

pixel

pixel

23 ms

Accessibility Review

whoisredjohn.com accessibility score

85

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

whoisredjohn.com best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

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

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

whoisredjohn.com

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