Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

johnargo.com

John Argo aka John T. Cullen a San Diego Author at Clocktower Books

Page Load Speed

794 ms in total

First Response

157 ms

Resources Loaded

428 ms

Page Rendered

209 ms

johnargo.com screenshot

About Website

Visit johnargo.com now to see the best up-to-date John Argo content and also check out these interesting facts you probably never knew about johnargo.com

John Argo has been online since 1996. He was the first person in history to publish HTML novels online to be read in HTML. Criteria: Proprietary novels, not public domain; published entirely online to...

Visit johnargo.com

Key Findings

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

johnargo.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

johnargo.com

157 ms

partner.js

247 ms

show_afd_ads.js

20 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Johnargo.com, 33% (1 request) were made to 050005.voodoo.com and 33% (1 request) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (247 ms) relates to the external source 050005.voodoo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 397 B (14%)

Content Size

2.8 kB

After Optimization

2.4 kB

In fact, the total size of Johnargo.com main page is 2.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 1.9 kB which makes up the majority of the site volume.

HTML Optimization

-34%

Potential reduce by 310 B

  • Original 919 B
  • After minification 917 B
  • After compression 609 B

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 310 B or 34% of the original size.

JavaScript Optimization

-5%

Potential reduce by 87 B

  • Original 1.9 kB
  • After minification 1.9 kB
  • After compression 1.8 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.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of John Argo. According to our analytics all requests are already optimized.

Accessibility Review

johnargo.com accessibility score

68

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

<frame> or <iframe> elements do not have a title

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

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

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

johnargo.com SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Johnargo.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 Johnargo.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 description is not detected on the main page of John Argo. 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: