Tools & Wizards About Us
historicalatlas.com screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

historicalatlas.com

HistoricalAtlas.com: The CENTENNIA Historical Atlas, Europe and the Middle East, 1000AD to the Present

Page Load Speed

2.4 sec in total

First Response

447 ms

Resources Loaded

1.3 sec

Page Rendered

678 ms

historicalatlas.com screenshot

About Website

Click here to check amazing Historical Atlas content. Otherwise, check out these important facts you probably never knew about historicalatlas.com

Centennia Historical Atlas: software app for Windows and MacOS, an animated dynamic guide to the history of Europe and the Middle East from 1000AD to the present.

Visit historicalatlas.com

Key Findings

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

Performance Metrics

historicalatlas.com performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

historicalatlas.com

447 ms

global-vars.css

142 ms

site-main.css

204 ms

dropdown.css

148 ms

site-exceptions.css

146 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Historicalatlas.com and no external sources were called. The less responsive or slowest element that took the longest time to load (447 ms) belongs to the original domain Historicalatlas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 139.6 kB (69%)

Content Size

202.9 kB

After Optimization

63.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Historicalatlas.com main page is 202.9 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 158.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 23.0 kB

  • Original 32.6 kB
  • After minification 31.0 kB
  • After compression 9.6 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 23.0 kB or 71% of the original size.

Image Optimization

-20%

Potential reduce by 1.2 kB

  • Original 5.8 kB
  • After minification 4.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. Obviously, Historical Atlas needs image optimization as it can save up to 1.2 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 113.0 kB

  • Original 158.6 kB
  • After minification 158.6 kB
  • After compression 45.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 113.0 kB or 71% of the original size.

CSS Optimization

-40%

Potential reduce by 2.4 kB

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

Requests Breakdown

Number of requests can be reduced by 3 (23%)

Requests Now

13

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

historicalatlas.com

historicalatlas.com

447 ms

global-vars.css

global-vars.css

142 ms

site-main.css

site-main.css

204 ms

dropdown.css

dropdown.css

148 ms

site-exceptions.css

site-exceptions.css

146 ms

top_up-min.js

top_up-min.js

380 ms

all.js

all.js

251 ms

logo-final-white.png

logo-final-white.png

92 ms

threebars.svg

threebars.svg

70 ms

roll-dice-E.jpg

roll-dice-E.jpg

82 ms

roll-dice-C.jpg

roll-dice-C.jpg

80 ms

threedots-light.svg

threedots-light.svg

93 ms

fb-ha-0.png

fb-ha-0.png

89 ms

loader.gif

loader.gif

141 ms

Accessibility Review

historicalatlas.com accessibility score

79

Accessibility Issues

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.

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

historicalatlas.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

historicalatlas.com SEO score

75

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

historicalatlas.com

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