21.1 sec in total
239 ms
20.6 sec
263 ms
Click here to check amazing Classic Car Database content for United States. Otherwise, check out these important facts you probably never knew about classiccardatabase.com
Specifications for classic autos, antique cars, vintage cars, old cars and muscle cars - American cars 1910 to 1975 - over 33,000 models. Includes, engine/transmission data, wheelbase, production nos....
Visit classiccardatabase.comWe analyzed Classiccardatabase.com page load time and found that the first response time was 239 ms and then it took 20.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
classiccardatabase.com performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value5.9 s
14/100
25%
Value3.2 s
92/100
10%
Value2,300 ms
5/100
30%
Value0
100/100
15%
Value7.7 s
45/100
10%
239 ms
53 ms
54 ms
54 ms
220 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Classiccardatabase.com, 10% (8 requests) were made to Tpc.googlesyndication.com and 10% (8 requests) were made to Barnebys.imgix.net. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Hostingprod.com.
Page size can be reduced by 1.0 MB (39%)
2.6 MB
1.6 MB
In fact, the total size of Classiccardatabase.com main page is 2.6 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. 65% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 40.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. This page needs HTML code to be minified as it can gain 5.7 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 40.2 kB or 75% of the original size.
Potential reduce by 50.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. Classic Car Database images are well optimized though.
Potential reduce by 734.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 734.6 kB or 63% of the original size.
Potential reduce by 214.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. Classiccardatabase.com needs all CSS files to be minified and compressed as it can save up to 214.3 kB or 83% of the original size.
Number of requests can be reduced by 36 (55%)
66
30
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classic Car Database. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
classiccardatabase.com
239 ms
search.js
53 ms
layout.css
54 ms
search.css
54 ms
whv2_001.js
220 ms
show_ads.js
2 ms
geov2.js
20319 ms
ga.js
6 ms
t_logo-a.png
63 ms
page4.jpg
53 ms
banner_900x141.png
131 ms
SEMA-Member-Logo.jpg
80 ms
CCDB%20799%20ad.png
52 ms
1934_Duesenberg.jpg
84 ms
1958_Edsel.jpg
54 ms
1968_Ford_GT_Torino.jpg
78 ms
HudsonPacemaker1950.jpg
88 ms
HudsonPacemaker1950p2.jpg
90 ms
featured-cars.png
138 ms
__utm.gif
10 ms
print.css
34 ms
visit.gif
100 ms
zrt_lookup.html
33 ms
show_ads_impl.js
32 ms
ads
224 ms
osd.js
32 ms
425 ms
plusone.js
50 ms
cb=gapi.loaded_0
6 ms
cb=gapi.loaded_1
18 ms
fastbutton
74 ms
postmessageRelay
40 ms
971028622-postmessagerelay.js
38 ms
rpc:shindig_random.js
37 ms
rs=AGLTcCOnDxwX8-LbpDmaxOBIoHm7W_kGNA
8 ms
cb=gapi.loaded_0
3 ms
css
55 ms
m_js_controller.js
45 ms
abg.js
44 ms
m_window_focus_non_hydra.js
50 ms
osd_listener.js
50 ms
m_qs_click_protection.js
50 ms
nessie_icon_tiamat_black.png
50 ms
iconx2-000000.png
40 ms
googlelogo_dark_color_84x28dp.png
49 ms
s
34 ms
x_button_blue2.png
9 ms
transparent.png
8 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
28 ms
fpJ246J2fJ0bYHH6KdX6NZQGrKMRoryxUcO6omD8DP8.js
2 ms
skyscraper120.css
51 ms
jquery-1.12.0.min.js
37 ms
jquery-migrate-1.2.1.min.js
34 ms
eim0xoc.js
27 ms
slick.css
26 ms
slick-theme.css
78 ms
slick.min.js
29 ms
analytics.js
104 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F8%2F25%2Fc%2F9%2F6%2Fc9693da1-b70e-4738-931c-21e1650727a1.jpg
154 ms
imp
103 ms
ajax-loader.gif
183 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F6%2F5%2F7%2Ff%2F8%2F7f838c71-8d37-402d-8cd7-4fc4b0fca1b5.jpg
132 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F8%2F20%2F0%2F1%2Ff%2F01f536f8-c463-4231-b6f2-1419e92bde29.jpg
85 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F8%2F29%2F8%2F7%2Fd%2F87d96767-e09d-4b8e-a202-92cf02ffcb18.jpg
98 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F8%2F22%2F0%2Fe%2F2%2F0e2530c7-2ac5-4332-ad36-c0e1ecbaf369.jpg
129 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F5%2F29%2F0%2F2%2F4%2F02467855-1259-4513-997b-3af34fb0fa8e.jpg
91 ms
https%3A%2F%2Fassets.catawiki.nl%2Fassets%2F2017%2F7%2F18%2F3%2Ff%2F2%2F3f2ce173-9487-429b-80aa-50e77e309b13.jpg
127 ms
http%3A%2F%2Fpictures.abebooks.com%2FBTYW%2Fmd%2Fmd21895046695.jpg
154 ms
slick.woff
56 ms
i
110 ms
i
106 ms
i
95 ms
i
106 ms
i
109 ms
i
104 ms
inv.gif
148 ms
collect
44 ms
classiccardatabase.com accessibility score
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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
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
classiccardatabase.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
classiccardatabase.com SEO score
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classiccardatabase.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 Classiccardatabase.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.
classiccardatabase.com
Open Graph description is not detected on the main page of Classic Car Database. 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: