Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

hyperhistory.com

World History : HyperHistory

Page Load Speed

1.1 sec in total

First Response

140 ms

Resources Loaded

863 ms

Page Rendered

97 ms

hyperhistory.com screenshot

About Website

Click here to check amazing Hyper History content for United States. Otherwise, check out these important facts you probably never knew about hyperhistory.com

World History Online navigates through 3 000 years of world history, world timelines of civilizations (plus maps), people and world events.

Visit hyperhistory.com

Key Findings

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

Performance Metrics

hyperhistory.com performance score

0

Network Requests Diagram

hyperhistory.com

140 ms

a.html

47 ms

stats.js

44 ms

piwik.js

259 ms

navbar.html

46 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Hyperhistory.com, 7% (2 requests) were made to Stats.starfall.com. The less responsive or slowest element that took the longest time to load (259 ms) relates to the external source Stats.starfall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.3 kB (7%)

Content Size

159.2 kB

After Optimization

148.8 kB

In fact, the total size of Hyperhistory.com main page is 159.2 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. Images take 134.8 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 1.1 kB

  • Original 1.6 kB
  • After minification 1.3 kB
  • After compression 586 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. This page needs HTML code to be minified as it can gain 299 B, which is 18% 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 1.1 kB or 64% of the original size.

Image Optimization

-6%

Potential reduce by 8.7 kB

  • Original 134.8 kB
  • After minification 126.1 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. Hyper History images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 390 B

  • Original 22.4 kB
  • After minification 22.2 kB
  • After compression 22.0 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

-55%

Potential reduce by 184 B

  • Original 333 B
  • After minification 310 B
  • After compression 149 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. Hyperhistory.com needs all CSS files to be minified and compressed as it can save up to 184 B or 55% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

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

Accessibility Review

hyperhistory.com accessibility score

33

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

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

SEO Factors

hyperhistory.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

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

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