Tools & Wizards About Us
worldwar-1.net screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

worldwar-1.net

World War 1 Timeline 1914-1919 - Worldwar-1.net

Page Load Speed

10.8 sec in total

First Response

155 ms

Resources Loaded

10.5 sec

Page Rendered

97 ms

worldwar-1.net screenshot

About Website

Welcome to worldwar-1.net homepage info - get ready to check World War 1 best content right away, or after learning these important things about worldwar-1.net

Worldwar-1.net is a complete World War 1 Timeline, detailing every event, day by day through World War I from 1914 through to 1919.

Visit worldwar-1.net

Key Findings

We analyzed Worldwar-1.net page load time and found that the first response time was 155 ms and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

worldwar-1.net performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

worldwar-1.net

155 ms

gppstub.js

89 ms

boise.js

88 ms

abilene.js

106 ms

world-war-1.css

28 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 80% of them (48 requests) were addressed to the original Worldwar-1.net, 5% (3 requests) were made to Google.com and 3% (2 requests) were made to The.gatekeeperconsent.com. The less responsive or slowest element that took the longest time to load (10.3 sec) relates to the external source Videouniverse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 42.2 kB (28%)

Content Size

148.6 kB

After Optimization

106.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Worldwar-1.net main page is 148.6 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 52.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 36.4 kB

  • Original 47.9 kB
  • After minification 43.9 kB
  • After compression 11.5 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 36.4 kB or 76% of the original size.

Image Optimization

-10%

Potential reduce by 5.2 kB

  • Original 52.8 kB
  • After minification 47.6 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. World War 1 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 376 B

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

-12%

Potential reduce by 155 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.2 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. Worldwar-1.net needs all CSS files to be minified and compressed as it can save up to 155 B or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (59%)

Requests Now

54

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

worldwar-1.net

worldwar-1.net

155 ms

gppstub.js

gppstub.js

89 ms

boise.js

boise.js

88 ms

abilene.js

abilene.js

106 ms

world-war-1.css

world-war-1.css

28 ms

ccpaplus.js

ccpaplus.js

101 ms

jsapi

jsapi

23 ms

brand

brand

40 ms

loader.js

loader.js

54 ms

t13n

t13n

114 ms

205486.jpg

205486.jpg

16 ms

88x31_video01.gif

88x31_video01.gif

10271 ms

world-war-1-title.gif

world-war-1-title.gif

155 ms

worldwar-1.gif

worldwar-1.gif

224 ms

timelines.gif

timelines.gif

155 ms

worldwar-2.gif

worldwar-2.gif

172 ms

world-war-1-photo.JPG

world-war-1-photo.JPG

75 ms

introduction.gif

introduction.gif

121 ms

belgium.GIF

belgium.GIF

106 ms

turkey.GIF

turkey.GIF

124 ms

france.GIF

france.GIF

174 ms

usa.GIF

usa.GIF

157 ms

austria-hungary.GIF

austria-hungary.GIF

178 ms

uk.GIF

uk.GIF

178 ms

australia.GIF

australia.GIF

185 ms

russia.GIF

russia.GIF

198 ms

italy.GIF

italy.GIF

203 ms

luxembourg.GIF

luxembourg.GIF

202 ms

new-zealand.GIF

new-zealand.GIF

210 ms

bulgaria.GIF

bulgaria.GIF

216 ms

canada.GIF

canada.GIF

214 ms

germany.GIF

germany.GIF

237 ms

serbia.GIF

serbia.GIF

227 ms

greece.GIF

greece.GIF

232 ms

romania.GIF

romania.GIF

243 ms

montenegro.GIF

montenegro.GIF

251 ms

albania.GIF

albania.GIF

247 ms

japan.GIF

japan.GIF

252 ms

world-war-1-recent-updates.gif

world-war-1-recent-updates.gif

358 ms

world-war-1-this-month.gif

world-war-1-this-month.gif

315 ms

german-fokker-dr1.jpg

german-fokker-dr1.jpg

330 ms

world-war-1-copyright.gif

world-war-1-copyright.gif

338 ms

brandjs.js

brandjs.js

49 ms

xaramenu.js

xaramenu.js

178 ms

worldwar1.js

worldwar1.js

177 ms

branding.png

branding.png

4 ms

worldwar1_left.png

worldwar1_left.png

120 ms

worldwar1_b1_over.png

worldwar1_b1_over.png

102 ms

worldwar1_b1.png

worldwar1_b1.png

171 ms

worldwar1_b2_over.png

worldwar1_b2_over.png

236 ms

worldwar1_b2.png

worldwar1_b2.png

137 ms

worldwar1_b3_over.png

worldwar1_b3_over.png

294 ms

worldwar1_b3.png

worldwar1_b3.png

239 ms

worldwar1_b4_over.png

worldwar1_b4_over.png

261 ms

worldwar1_b4.png

worldwar1_b4.png

243 ms

worldwar1_b5_over.png

worldwar1_b5_over.png

292 ms

worldwar1_b5.png

worldwar1_b5.png

361 ms

worldwar1_b6_over.png

worldwar1_b6_over.png

340 ms

worldwar1_b6.png

worldwar1_b6.png

336 ms

worldwar1_right.png

worldwar1_right.png

384 ms

Accessibility Review

worldwar-1.net accessibility score

55

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

worldwar-1.net best practices score

58

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

worldwar-1.net SEO score

69

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

    N/A

  • Encoding

    ISO-8859-1

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

worldwar-1.net

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