Tools & Wizards About Us
archivemaps.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

archivemaps.com

MAPCO : Map And Plan Collection Online

Page Load Speed

31.4 sec in total

First Response

226 ms

Resources Loaded

14.9 sec

Page Rendered

16.3 sec

archivemaps.com screenshot

About Website

Visit archivemaps.com now to see the best up-to-date Archive Map S content and also check out these interesting facts you probably never knew about archivemaps.com

High resolution scans from the David Hale Map Collection.

Visit archivemaps.com

Key Findings

We analyzed Archivemaps.com page load time and found that the first response time was 226 ms and then it took 31.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

archivemaps.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value2,790 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.4 s

15/100

10%

Network Requests Diagram

archivemaps.com

226 ms

mapco.net

228 ms

colours.css

285 ms

show_ads.js

22 ms

addthis_widget.js

198 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Archivemaps.com, 43% (19 requests) were made to Mapco.net and 14% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Paypal.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 541.8 kB (43%)

Content Size

1.3 MB

After Optimization

711.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 37.2 kB

  • Original 48.4 kB
  • After minification 48.1 kB
  • After compression 11.2 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 37.2 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 17.0 kB

  • Original 419.7 kB
  • After minification 402.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. Archive Map S images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 483.5 kB

  • Original 780.5 kB
  • After minification 780.5 kB
  • After compression 297.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 483.5 kB or 62% of the original size.

CSS Optimization

-88%

Potential reduce by 4.1 kB

  • Original 4.7 kB
  • After minification 3.7 kB
  • After compression 558 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. Archivemaps.com needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (33%)

Requests Now

42

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

archivemaps.com

archivemaps.com

226 ms

mapco.net

mapco.net

228 ms

colours.css

colours.css

285 ms

show_ads.js

show_ads.js

22 ms

addthis_widget.js

addthis_widget.js

198 ms

headred2.jpg

headred2.jpg

799 ms

adheight.gif

adheight.gif

798 ms

counter.js

counter.js

943 ms

btn_donateCC_LG.gif

btn_donateCC_LG.gif

4986 ms

lg-bookmark-en.gif

lg-bookmark-en.gif

711 ms

northadelaidepanorama001t3.jpg

northadelaidepanorama001t3.jpg

1059 ms

rundle001t.jpg

rundle001t.jpg

1058 ms

clarec1880bt.jpg

clarec1880bt.jpg

1060 ms

pixel.gif

pixel.gif

6027 ms

bgcompass.jpg

bgcompass.jpg

710 ms

weller1868hd.jpg

weller1868hd.jpg

759 ms

mapco.jpg

mapco.jpg

759 ms

imcos.jpg

imcos.jpg

759 ms

myspace_icon.png

myspace_icon.png

760 ms

twitter_icon.png

twitter_icon.png

760 ms

facebook_icon.png

facebook_icon.png

760 ms

geologicalt02.jpg

geologicalt02.jpg

1057 ms

stanford1864lt.jpg

stanford1864lt.jpg

1056 ms

london1868tl.jpg

london1868tl.jpg

1057 ms

stanford1878lt.jpg

stanford1878lt.jpg

2448 ms

date.gif

date.gif

2448 ms

Count.cgi

Count.cgi

2448 ms

copyright.gif

copyright.gif

2444 ms

ca-pub-8363095175045143.js

ca-pub-8363095175045143.js

5461 ms

zrt_lookup.html

zrt_lookup.html

5220 ms

show_ads_impl.js

show_ads_impl.js

2699 ms

bg.gif

bg.gif

3576 ms

ads

ads

3298 ms

osd.js

osd.js

2772 ms

ads

ads

2961 ms

ads

ads

2473 ms

ads

ads

1367 ms

ads

ads

772 ms

abg.js

abg.js

1333 ms

osd_listener.js

osd_listener.js

1597 ms

t.php

t.php

844 ms

_ate.track.config_resp

_ate.track.config_resp

578 ms

300lo.json

300lo.json

754 ms

sh.48536d49e4da3bdba54606b4.html

sh.48536d49e4da3bdba54606b4.html

1193 ms

Accessibility Review

archivemaps.com accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

archivemaps.com 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

High

Browser errors were logged to the console

SEO Factors

archivemaps.com SEO score

77

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

archivemaps.com

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