Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

unithistories.com

World War II unit histories & officers

Page Load Speed

1 sec in total

First Response

296 ms

Resources Loaded

557 ms

Page Rendered

162 ms

unithistories.com screenshot

About Website

Visit unithistories.com now to see the best up-to-date Unit Histories content for United Kingdom and also check out these interesting facts you probably never knew about unithistories.com

Details on World War II fighting unit histories, including organization, commanders and literature.

Visit unithistories.com

Key Findings

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

Performance Metrics

unithistories.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.1 s

100/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.1 s

100/100

10%

Network Requests Diagram

unithistories.com

296 ms

style.css

87 ms

all.js

171 ms

achtergrond.jpeg

87 ms

frame03.jpg

167 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 89% of them (8 requests) were addressed to the original Unithistories.com, 11% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (296 ms) belongs to the original domain Unithistories.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.2 kB (14%)

Content Size

44.0 kB

After Optimization

37.9 kB

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

HTML Optimization

-60%

Potential reduce by 2.5 kB

  • Original 4.1 kB
  • After minification 3.8 kB
  • After compression 1.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 2.5 kB or 60% of the original size.

Image Optimization

-2%

Potential reduce by 345 B

  • Original 17.8 kB
  • After minification 17.4 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. Unit Histories images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 1.9 kB

  • Original 20.2 kB
  • After minification 19.7 kB
  • After compression 18.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. This website has mostly compressed JavaScripts.

CSS Optimization

-73%

Potential reduce by 1.5 kB

  • Original 2.0 kB
  • After minification 1.5 kB
  • After compression 548 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. Unithistories.com needs all CSS files to be minified and compressed as it can save up to 1.5 kB or 73% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

8

After Optimization

8

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

Accessibility Review

unithistories.com accessibility score

94

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

unithistories.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 Unithistories.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 Unithistories.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 Unit Histories. 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: