Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

johnhorse.com

Rebellion: John Horse and the Black Seminoles, First Black Rebels to Beat American Slavery

Page Load Speed

647 ms in total

First Response

112 ms

Resources Loaded

446 ms

Page Rendered

89 ms

About Website

Welcome to johnhorse.com homepage info - get ready to check John Horse best content for United States right away, or after learning these important things about johnhorse.com

Web documentary on John Horse and the Black Seminoles, first black rebels to beat American slavery and leaders of the largest slave rebellion in U.S. history.

Visit johnhorse.com

Key Findings

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

johnhorse.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

johnhorse.com

112 ms

main.css

40 ms

show_ads.js

86 ms

counter.js

22 ms

bg3mapseat.jpg

117 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 82% of them (18 requests) were addressed to the original Johnhorse.com, 9% (2 requests) were made to Pagead2.googlesyndication.com and 5% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (266 ms) belongs to the original domain Johnhorse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 18.3 kB (12%)

Content Size

157.9 kB

After Optimization

139.6 kB

In fact, the total size of Johnhorse.com main page is 157.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. 15% of websites need less resources to load. Javascripts take 80.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 17.7 kB

  • Original 22.5 kB
  • After minification 19.4 kB
  • After compression 4.8 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 3.1 kB, which is 14% 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 17.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 121 B

  • Original 53.0 kB
  • After minification 52.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. John Horse images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 40 B

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

-31%

Potential reduce by 440 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 991 B

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. Johnhorse.com needs all CSS files to be minified and compressed as it can save up to 440 B or 31% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

21

After Optimization

21

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

Accessibility Review

johnhorse.com accessibility score

77

Accessibility Issues

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

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

Form elements do not have associated labels

Best Practices

johnhorse.com best practices score

67

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

Page has valid source maps

SEO Factors

johnhorse.com SEO score

67

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnhorse.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 Johnhorse.com main page’s claimed encoding is . 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

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