Tools & Wizards About Us
tank100.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tank100.com

Tank 100 Archives - The Tank Museum

Page Load Speed

2.3 sec in total

First Response

43 ms

Resources Loaded

1.3 sec

Page Rendered

916 ms

tank100.com screenshot

About Website

Welcome to tank100.com homepage info - get ready to check Tank 100 best content right away, or after learning these important things about tank100.com

Visit tank100.com

Key Findings

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

Performance Metrics

tank100.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.216

58/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

tank100.com

43 ms

tank-100

108 ms

uc.js

40 ms

style.min.css

32 ms

image-map-pro.min.css

101 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tank100.com, 88% (71 requests) were made to Tankmuseum.org and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (762 ms) relates to the external source Tankmuseum.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.2 kB (3%)

Content Size

3.2 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tank100.com main page is 3.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. 80% 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 91.3 kB

  • Original 112.8 kB
  • After minification 112.7 kB
  • After compression 21.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 91.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.7 MB
  • After minification 2.7 MB

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. Tank 100 images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 10.9 kB

  • Original 230.0 kB
  • After minification 230.0 kB
  • After compression 219.0 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

-2%

Potential reduce by 3.0 kB

  • Original 149.3 kB
  • After minification 149.3 kB
  • After compression 146.3 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. Tank100.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (53%)

Requests Now

75

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tank100.com

tank100.com

43 ms

tank-100

tank-100

108 ms

uc.js

uc.js

40 ms

style.min.css

style.min.css

32 ms

image-map-pro.min.css

image-map-pro.min.css

101 ms

frontend.min.css

frontend.min.css

51 ms

ultimeter-public.css

ultimeter-public.css

90 ms

child-theme.min.css

child-theme.min.css

55 ms

style.min.css

style.min.css

51 ms

js_composer.min.css

js_composer.min.css

73 ms

wprevpro_w3_min.css

wprevpro_w3_min.css

97 ms

jquery.min.js

jquery.min.js

90 ms

jquery-migrate.min.js

jquery-migrate.min.js

91 ms

slick.min.js

slick.min.js

122 ms

infiniteslidev2.min.js

infiniteslidev2.min.js

91 ms

wprs-slick.min.js

wprs-slick.min.js

120 ms

wprs-combined.min.js

wprs-combined.min.js

126 ms

wprev-public.min.js

wprev-public.min.js

125 ms

analytics.js

analytics.js

47 ms

js

js

88 ms

js

js

125 ms

slick-theme.css

slick-theme.css

305 ms

slick.css

slick.css

149 ms

image-map-pro.min.js

image-map-pro.min.js

304 ms

ultimeter-public.js

ultimeter-public.js

294 ms

core.min.js

core.min.js

294 ms

accordion.min.js

accordion.min.js

303 ms

menu.min.js

menu.min.js

303 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

301 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

301 ms

wp-polyfill.min.js

wp-polyfill.min.js

374 ms

dom-ready.min.js

dom-ready.min.js

367 ms

hooks.min.js

hooks.min.js

385 ms

i18n.min.js

i18n.min.js

367 ms

a11y.min.js

a11y.min.js

366 ms

autocomplete.min.js

autocomplete.min.js

364 ms

child-theme.min.js

child-theme.min.js

368 ms

js_composer_front.min.js

js_composer_front.min.js

396 ms

custom.js

custom.js

433 ms

app.min.js

app.min.js

393 ms

fbevents.js

fbevents.js

214 ms

events.js

events.js

243 ms

hotjar-2281200.js

hotjar-2281200.js

284 ms

Gear-0.3s-100px.svg

Gear-0.3s-100px.svg

305 ms

TM_Logo.png

TM_Logo.png

262 ms

ticket.svg

ticket.svg

271 ms

search-icon.svg

search-icon.svg

273 ms

News-Articles-1440x500.jpg

News-Articles-1440x500.jpg

437 ms

Untitled-design-69.png

Untitled-design-69.png

413 ms

0927-F4-Hero-Image-768x267.png

0927-F4-Hero-Image-768x267.png

414 ms

Early-crewed-version-2501-A1-featured.jpg

Early-crewed-version-2501-A1-featured.jpg

413 ms

featured-use-this-one.jpg

featured-use-this-one.jpg

480 ms

Featured-image.jpg

Featured-image.jpg

435 ms

Fray-Bentos-Featured-768x407.jpg

Fray-Bentos-Featured-768x407.jpg

540 ms

Feature-1-768x407.jpg

Feature-1-768x407.jpg

589 ms

Paint-and-camouflage-featured-image.jpg

Paint-and-camouflage-featured-image.jpg

589 ms

making-a-Mark-IV-featured-image-768x409.jpg

making-a-Mark-IV-featured-image-768x409.jpg

583 ms

Cav-passing-Mk-V-featured.jpg

Cav-passing-Mk-V-featured.jpg

582 ms

Petrol-tanks-header-feature.jpg

Petrol-tanks-header-feature.jpg

610 ms

PE1984-featured.jpg

PE1984-featured.jpg

673 ms

collect

collect

81 ms

E1978-featured.jpg

E1978-featured.jpg

589 ms

featured.jpg

featured.jpg

578 ms

Lato-Regular.ttf

Lato-Regular.ttf

499 ms

Lato-Bold.ttf

Lato-Bold.ttf

457 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

588 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

603 ms

Whippet18.jpg-featured.jpg

Whippet18.jpg-featured.jpg

659 ms

A7V_8929-T6-IH-JM-Edit-featured.jpg

A7V_8929-T6-IH-JM-Edit-featured.jpg

541 ms

C-Bn-female238-featured.jpg

C-Bn-female238-featured.jpg

656 ms

0867-A1.jpg-featured.jpg

0867-A1.jpg-featured.jpg

633 ms

Featured.jpg

Featured.jpg

680 ms

featured-1.jpg

featured-1.jpg

713 ms

main.MTZlYmMyNjliMQ.js

main.MTZlYmMyNjliMQ.js

10 ms

tanks-logo-footer.png

tanks-logo-footer.png

662 ms

tiktok.svg

tiktok.svg

627 ms

patreon-new.svg

patreon-new.svg

636 ms

Website_Logo.png

Website_Logo.png

735 ms

LogosArtboard-4-1.png

LogosArtboard-4-1.png

730 ms

Heritage-lottery-fund-cropped-1.png

Heritage-lottery-fund-cropped-1.png

762 ms

ajax-loader.gif

ajax-loader.gif

502 ms

Accessibility Review

tank100.com accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

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

tank100.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tank100.com SEO score

93

Search Engine Optimization Advices

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

tank100.com

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