Tools & Wizards About Us
antique-locks.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

antique-locks.com

The Antique Locks Forum - Industrial Archeology of locks.

Page Load Speed

4.2 sec in total

First Response

727 ms

Resources Loaded

2.8 sec

Page Rendered

621 ms

antique-locks.com screenshot

About Website

Click here to check amazing Antique Locks content for United States. Otherwise, check out these important facts you probably never knew about antique-locks.com

www.antique-locks.com, the premier site for those seeking technical/historical information on locks, keys & safes etc.

Visit antique-locks.com

Key Findings

We analyzed Antique-locks.com page load time and found that the first response time was 727 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

antique-locks.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value2.4 s

98/100

10%

Network Requests Diagram

forum.php

727 ms

tapatalkdetect.js

156 ms

vbulletin-core.js

317 ms

css.php

722 ms

vbulletin_read_marker.js

169 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 79% of them (42 requests) were addressed to the original Antique-locks.com, 19% (10 requests) were made to Emorlands.com and 2% (1 request) were made to Historyoflocks.com. The less responsive or slowest element that took the longest time to load (759 ms) relates to the external source Historyoflocks.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.1 kB (36%)

Content Size

993.3 kB

After Optimization

639.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Antique-locks.com main page is 993.3 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. 20% of websites need less resources to load. Images take 637.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 71.9 kB

  • Original 85.6 kB
  • After minification 77.7 kB
  • After compression 13.7 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 71.9 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 76.1 kB

  • Original 637.2 kB
  • After minification 561.2 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, Antique Locks needs image optimization as it can save up to 76.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 103.6 kB

  • Original 151.0 kB
  • After minification 149.5 kB
  • After compression 47.4 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 103.6 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 102.5 kB

  • Original 119.5 kB
  • After minification 93.2 kB
  • After compression 17.0 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. Antique-locks.com needs all CSS files to be minified and compressed as it can save up to 102.5 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (63%)

Requests Now

46

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forum.php

forum.php

727 ms

tapatalkdetect.js

tapatalkdetect.js

156 ms

vbulletin-core.js

vbulletin-core.js

317 ms

css.php

css.php

722 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

169 ms

css.php

css.php

403 ms

css.php

css.php

457 ms

vbulletin_md5.js

vbulletin_md5.js

248 ms

animation-min.js

animation-min.js

411 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

315 ms

connection-min.js

connection-min.js

405 ms

hllogo.jpg

hllogo.jpg

608 ms

COLTiglobe.jpg

COLTiglobe.jpg

612 ms

msp.jpg

msp.jpg

609 ms

tlcn3-1.jpg

tlcn3-1.jpg

612 ms

tlcn3-2.jpg

tlcn3-2.jpg

610 ms

tophead1.jpg

tophead1.jpg

313 ms

logo.gif

logo.gif

88 ms

search.png

search.png

89 ms

navbit-home.png

navbit-home.png

89 ms

collapse_40b.png

collapse_40b.png

90 ms

forum_old-48.png

forum_old-48.png

89 ms

icon1.png

icon1.png

159 ms

lastpost-right.png

lastpost-right.png

161 ms

icon5.png

icon5.png

166 ms

forum_stats.png

forum_stats.png

166 ms

legend.png

legend.png

167 ms

forum_new-16.png

forum_new-16.png

236 ms

forum_old-16.png

forum_old-16.png

237 ms

category-16.png

category-16.png

244 ms

forum_link-16.png

forum_link-16.png

246 ms

widget-comment.png

widget-comment.png

244 ms

unknown.gif

unknown.gif

315 ms

image.php

image.php

416 ms

image.php

image.php

465 ms

widget-forum.png

widget-forum.png

326 ms

image.php

image.php

461 ms

cron.php

cron.php

625 ms

head5.jpg

head5.jpg

759 ms

navbar1.jpg

navbar1.jpg

557 ms

newbtn_middle.png

newbtn_middle.png

352 ms

selected-tab-gradient-with-top-alpha.png

selected-tab-gradient-with-top-alpha.png

426 ms

arrow.png

arrow.png

427 ms

grey-up.png

grey-up.png

474 ms

gradient-greytowhite.png

gradient-greytowhite.png

472 ms

top-highlight.png

top-highlight.png

495 ms

gradient-black-down.png

gradient-black-down.png

503 ms

bottom-shadow.png

bottom-shadow.png

541 ms

hllogo.jpg

hllogo.jpg

314 ms

msp.jpg

msp.jpg

160 ms

tlcn3-2.jpg

tlcn3-2.jpg

388 ms

COLTiglobe.jpg

COLTiglobe.jpg

234 ms

tlcn3-1.jpg

tlcn3-1.jpg

394 ms

Accessibility Review

antique-locks.com accessibility score

53

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

antique-locks.com best practices score

67

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

SEO Factors

antique-locks.com SEO score

67

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

    N/A

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Antique-locks.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Antique-locks.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

antique-locks.com

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