6 sec in total
404 ms
4.6 sec
981 ms
Visit wwiithenandnow.com now to see the best up-to-date WWII Then And Now content and also check out these interesting facts you probably never knew about wwiithenandnow.com
Photos from World War II events or places with a historical background. Then taken and now revisited. Also a shop with military collectables such as wings and patches.
Visit wwiithenandnow.comWe analyzed Wwiithenandnow.com page load time and found that the first response time was 404 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wwiithenandnow.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value6.5 s
9/100
25%
Value15.1 s
1/100
10%
Value1,820 ms
9/100
30%
Value0.059
98/100
15%
Value20.1 s
2/100
10%
404 ms
691 ms
188 ms
295 ms
285 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 59% of them (93 requests) were addressed to the original Wwiithenandnow.com, 34% (54 requests) were made to C0.wp.com and 2% (3 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (907 ms) belongs to the original domain Wwiithenandnow.com.
Page size can be reduced by 191.7 kB (9%)
2.2 MB
2.0 MB
In fact, the total size of Wwiithenandnow.com main page is 2.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 154.8 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 154.8 kB or 80% of the original size.
Potential reduce by 5.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. WWII Then And Now images are well optimized though.
Potential reduce by 18.9 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 12.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. Wwiithenandnow.com has all CSS files already compressed.
Number of requests can be reduced by 127 (86%)
148
21
The browser has sent 148 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WWII Then And Now. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 84 to 1 for JavaScripts and from 45 to 1 for CSS and as a result speed up the page load time.
wwiithenandnow.com
404 ms
www.wwiithenandnow.com
691 ms
remodal.css
188 ms
remodal-default-theme.css
295 ms
marker-library-dialog.css
285 ms
style-index.css
296 ms
custom-fonts.css
284 ms
style.min.css
77 ms
mediaelementplayer-legacy.min.css
75 ms
wp-mediaelement.min.css
81 ms
style.css
294 ms
wpmenucart-icons.min.css
284 ms
wpmenucart-main.min.css
381 ms
woocommerce-layout.css
79 ms
woocommerce.css
84 ms
photoswipe.css
381 ms
default-skin.css
379 ms
slick.css
391 ms
slick-theme.css
389 ms
wooswipe.css
388 ms
woo-multi-currency.min.css
473 ms
flags-64.min.css
475 ms
gateway.css
478 ms
style.css
484 ms
style.css
492 ms
genericons.css
79 ms
cff-style.min.css
494 ms
font-awesome.min.css
95 ms
app.css
567 ms
jetpack.css
88 ms
wp-polyfill-inert.min.js
87 ms
regenerator-runtime.min.js
88 ms
wp-polyfill.min.js
96 ms
hooks.min.js
96 ms
w.js
86 ms
jquery.min.js
95 ms
jquery-migrate.min.js
95 ms
remodal.min.js
598 ms
jquery.blockUI.min.js
106 ms
add-to-cart.min.js
105 ms
js.cookie.min.js
106 ms
woocommerce.min.js
106 ms
photoswipe.min.js
600 ms
photoswipe-ui-default.min.js
599 ms
slick.min.js
602 ms
wpgmza_data.js
601 ms
wp-hide-post-public.js
660 ms
woo-multi-currency.min.js
663 ms
js
132 ms
s-202404.js
83 ms
navigation.js
688 ms
wc-blocks.css
11 ms
font-awesome.min.css
649 ms
fa-5to4.css
649 ms
common.css
734 ms
jquery.dataTables.min.css
752 ms
legacy.css
751 ms
owl.carousel.min.css
754 ms
owl.theme.default.min.css
753 ms
sourcebuster.min.js
10 ms
order-attribution.min.js
11 ms
react.min.js
11 ms
deprecated.min.js
11 ms
dom.min.js
12 ms
react-dom.min.js
13 ms
escape-html.min.js
13 ms
element.min.js
14 ms
is-shallow-equal.min.js
14 ms
i18n.min.js
13 ms
keycodes.min.js
14 ms
priority-queue.min.js
15 ms
compose.min.js
15 ms
private-apis.min.js
16 ms
redux-routine.min.js
15 ms
data.min.js
15 ms
lodash.min.js
16 ms
wc-blocks-registry.js
17 ms
url.min.js
17 ms
api-fetch.min.js
19 ms
wc-settings.js
17 ms
data-controls.min.js
17 ms
html-entities.min.js
18 ms
notices.min.js
19 ms
wc-blocks-middleware.js
19 ms
wc-blocks-data.js
21 ms
dom-ready.min.js
19 ms
a11y.min.js
19 ms
primitives.min.js
21 ms
warning.min.js
22 ms
blocks-components.js
21 ms
e-202404.js
15 ms
js
82 ms
carousel_sky.css
746 ms
blocks-checkout.js
19 ms
order-attribution-blocks.min.js
19 ms
wc-blocks-google-analytics.js
19 ms
woocommerce-smallscreen.css
2 ms
featherlight.min.css
671 ms
dataTables.responsive.css
656 ms
wpgmaps-admin.css
662 ms
wpgmza_style_pro.css
652 ms
legacy-modern.css
642 ms
wooswipe.js
644 ms
button.js
747 ms
cff-scripts.min.js
651 ms
actions.js
649 ms
dummy.js
649 ms
jquery.dataTables.min.js
647 ms
dataTables.responsive.js
649 ms
jquery-cookie.js
735 ms
pep.js
654 ms
text.js
655 ms
pako_deflate.min.js
655 ms
wp-google-maps-pro.min.js
885 ms
kdTree-min.js
648 ms
cheap-ruler.js
728 ms
g.gif
22 ms
wp-google-maps-gold.min.js
626 ms
owl.carousel.js
628 ms
featherlight.min.js
624 ms
polyline.js
630 ms
CanvasLayerOptions.js
724 ms
CanvasLayer.js
718 ms
lib.core.js
662 ms
lib.view.js
640 ms
302349013_505169821569592_7887538543854183325_n.jpg
483 ms
client.js
590 ms
client.js
673 ms
tag.item.js
590 ms
tag.ui.js
577 ms
Genericons.svg
17 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
7 ms
fontawesome-webfont.woff
17 ms
handler.image.js
574 ms
lato-v14-latin-ext_latin-regular.woff
613 ms
lato-v14-latin-ext_latin-700.woff
655 ms
fjalla-one-v5-latin-ext_latin-regular.woff
667 ms
WPMenuCart.woff
667 ms
lato-v14-latin-ext_latin-700italic.woff
761 ms
lato-v14-latin-ext_latin-italic.woff
592 ms
bg_page.png
613 ms
main-picture-logo-small.jpg
907 ms
20230901_172001-1024x461.jpg
775 ms
20230901_171316-1024x461.jpg
730 ms
20230901_163204-461x1024.jpg
779 ms
20230901_160804-461x1024.jpg
709 ms
GridArt_20230528_141435166-1024x819.jpg
870 ms
Bombed-Havelte-fliegerhorst-1.jpg
874 ms
usaf-pilot-wing-200x200.jpg
778 ms
g.gif
11 ms
usaf-senior-pilot-wing-200x200.jpg
791 ms
usaf-command-pilot-wing-200x200.jpg
778 ms
army-air-corps-8th-air-force-square-200x200.jpg
795 ms
pa002-rangers-ww2-patch-200x107.jpg
814 ms
cff-avatar.png
821 ms
style.css
536 ms
style.css
538 ms
spotlight-poi3.png
511 ms
wwiithenandnow.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wwiithenandnow.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
wwiithenandnow.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wwiithenandnow.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 Wwiithenandnow.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.
wwiithenandnow.com
Open Graph data is detected on the main page of WWII Then And Now. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: