5.1 sec in total
1.4 sec
3.3 sec
430 ms
Visit war-memorial.net now to see the best up-to-date War Memorial content for Canada and also check out these interesting facts you probably never knew about war-memorial.net
The Polynational War Memorial is a conceptual and architectonic proposal for a global war memorial and a collection of of war memorials from all over the world.
Visit war-memorial.netWe analyzed War-memorial.net page load time and found that the first response time was 1.4 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
war-memorial.net performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value4.4 s
38/100
25%
Value6.6 s
37/100
10%
Value440 ms
64/100
30%
Value0.034
100/100
15%
Value10.4 s
24/100
10%
1396 ms
25 ms
101 ms
193 ms
192 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 53% of them (26 requests) were addressed to the original War-memorial.net, 12% (6 requests) were made to Tpc.googlesyndication.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain War-memorial.net.
Page size can be reduced by 222.8 kB (15%)
1.5 MB
1.3 MB
In fact, the total size of War-memorial.net main page is 1.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 993.0 kB which makes up the majority of the site volume.
Potential reduce by 36.9 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 5.6 kB, which is 11% 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 36.9 kB or 75% of the original size.
Potential reduce by 155.5 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, War Memorial needs image optimization as it can save up to 155.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 19.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. This website has mostly compressed JavaScripts.
Potential reduce by 10.8 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. War-memorial.net needs all CSS files to be minified and compressed as it can save up to 10.8 kB or 58% of the original size.
Number of requests can be reduced by 17 (38%)
45
28
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of War Memorial. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
war-memorial.net
1396 ms
css
25 ms
polystyle2013.css
101 ms
polystyle2016.css
193 ms
slider-pro.min.css
192 ms
jquery.fancybox.css
191 ms
examples.css
190 ms
jquery-1.11.0.min.js
399 ms
jquery.sliderPro.min.js
305 ms
jquery.fancybox.pack.js
288 ms
adsbygoogle.js
93 ms
counter.js
36 ms
head-2014-1.png
263 ms
404.asp
485 ms
orgvio_type23.png
1159 ms
184_20180804172302.jpg
231 ms
185_20180804172312.jpg
191 ms
186_20180804172322.jpg
289 ms
187_20180804172336.jpg
324 ms
206_20180804172348.jpg
282 ms
fb-rund-grey80.png
153 ms
twitter-rund-grey80.png
245 ms
OpenSans-Regular-webfont.woff
268 ms
sdk.js
113 ms
show_ads_impl.js
312 ms
_20140329123548.jpg
624 ms
_20140329121023.jpg
366 ms
_20140329102015.jpg
490 ms
_20140319204522.jpg
491 ms
_20140318210940.jpg
343 ms
354_20140314222622.JPG
436 ms
t.php
155 ms
openhand.cur
332 ms
sdk.js
9 ms
40 ms
zrt_lookup.html
30 ms
ads
380 ms
ads
170 ms
18078860953639259287
30 ms
icon.png
9 ms
abg_lite.js
19 ms
s
7 ms
window_focus.js
24 ms
qs_click_protection.js
24 ms
ufs_web_display.js
13 ms
one_click_handler_one_afma.js
138 ms
transparent.png
138 ms
activeview
61 ms
XKVjlGMZ-9Co2xOMMN0j_EFrFyX9juKw-kmGvwQcBeY.js
4 ms
war-memorial.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Form elements do not have associated labels
war-memorial.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
war-memorial.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise War-memorial.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 War-memorial.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.
war-memorial.net
Open Graph description is not detected on the main page of War Memorial. 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: