2.3 sec in total
167 ms
1.7 sec
471 ms
Visit classicbodyparts.com now to see the best up-to-date Classic Body Parts content and also check out these interesting facts you probably never knew about classicbodyparts.com
Classic car parts for your restoration project from brands such as Dynacorn, OER and more at everyday low prices! Inventory updated daily!
Visit classicbodyparts.comWe analyzed Classicbodyparts.com page load time and found that the first response time was 167 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.
classicbodyparts.com performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value8.5 s
2/100
25%
Value7.0 s
32/100
10%
Value2,030 ms
7/100
30%
Value0.134
80/100
15%
Value15.3 s
7/100
10%
167 ms
110 ms
32 ms
44 ms
114 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 76% of them (60 requests) were addressed to the original Classicbodyparts.com, 3% (2 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Bat.bing.com. The less responsive or slowest element that took the longest time to load (453 ms) belongs to the original domain Classicbodyparts.com.
Page size can be reduced by 156.7 kB (10%)
1.6 MB
1.5 MB
In fact, the total size of Classicbodyparts.com main page is 1.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. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 104.9 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 104.9 kB or 81% of the original size.
Potential reduce by 18.3 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 Body Parts images are well optimized though.
Potential reduce by 33.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 33.4 kB or 12% of the original size.
Number of requests can be reduced by 53 (71%)
75
22
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classic Body Parts. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
classicbodyparts.com
167 ms
hotjar-2702777.js
110 ms
loader.js
32 ms
style-index.css
44 ms
style-point-selection-block.css
114 ms
style.min.css
114 ms
metorik.css
42 ms
webfont.min.css
118 ms
public.min.css
123 ms
style.css
86 ms
style.css
104 ms
free-shipping.css
122 ms
style.css
138 ms
checkout-blocks.css
142 ms
search-forms.css
134 ms
wcwl_frontend.min.css
137 ms
dashicons.min.css
155 ms
woocommerce.css
153 ms
mailin-front.css
159 ms
wp-polyfill-inert.min.js
165 ms
regenerator-runtime.min.js
192 ms
wp-polyfill.min.js
169 ms
hooks.min.js
184 ms
w.js
23 ms
jquery.min.js
181 ms
jquery-migrate.min.js
179 ms
jquery.blockUI.min.js
184 ms
add-to-cart.min.js
189 ms
js.cookie.min.js
216 ms
woocommerce.min.js
314 ms
mailin-front.js
218 ms
sourcebuster.min.js
216 ms
order-attribution.min.js
217 ms
gtm4wp-ecommerce-generic.js
285 ms
gtm4wp-woocommerce.js
285 ms
metorik.min.js
286 ms
cart-fragments.min.js
285 ms
public.min.js
312 ms
vendor.min.js
323 ms
api.js
73 ms
custom.min.js
329 ms
index.js
295 ms
script.min.js
287 ms
css2
30 ms
wcwl_frontend.min.js
232 ms
wcwl_account.min.js
235 ms
modules.478d49d6cc21ec95d184.js
14 ms
g.gif
111 ms
gtm.js
197 ms
sa.js
189 ms
classic-body-parts-logo.png
176 ms
home-hero-camaro.jpg
293 ms
charger-hero.jpg
178 ms
shelby-cobra.jpg
224 ms
classic-car-is-in-a-workshop.jpg
177 ms
firebird.jpg
177 ms
9796808_main-01.jpg
278 ms
1704D.jpg
292 ms
3691476_main-01-1.jpg
287 ms
1114DC.jpg
278 ms
1967-MUSTANG-ELANOR-KIT.jpg
276 ms
1967-MUSTANG-FACTBACK-CONVERSION.jpg
291 ms
67-MUSTANG-FASTBACK-CONVERSION.jpg
291 ms
4227229_main-01.jpg
287 ms
cc-logos.png
340 ms
paypal-logo.png
339 ms
la-solid-900.woff
329 ms
la-regular-400.woff
453 ms
tinvwl-webfont.woff
442 ms
recaptcha__en.js
131 ms
bat.js
130 ms
js
75 ms
analytics.js
72 ms
137017805.js
68 ms
collect
12 ms
137017805
83 ms
collect
42 ms
clarity.js
15 ms
c.gif
8 ms
classicbodyparts.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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
classicbodyparts.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
classicbodyparts.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classicbodyparts.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 Classicbodyparts.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.
classicbodyparts.com
Open Graph data is detected on the main page of Classic Body Parts. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: