Tools & Wizards About Us
classicshoptalk.com screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

classicshoptalk.com

Classic Shop Talk - Classic Car and Truck Magazine, Forum, News, Talk, Cars, Trucks and Parts for Sale

Page Load Speed

4.9 sec in total

First Response

199 ms

Resources Loaded

4.3 sec

Page Rendered

348 ms

classicshoptalk.com screenshot

About Website

Welcome to classicshoptalk.com homepage info - get ready to check Classic Shop Talk best content right away, or after learning these important things about classicshoptalk.com

Classic Car and Truck Magazine, Forum, News, Talk, Cars, Trucks and Parts for Sale

Visit classicshoptalk.com

Key Findings

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

Performance Metrics

classicshoptalk.com performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value4.4 s

75/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

classicshoptalk.com

199 ms

www.classicshoptalk.com

1955 ms

yuiloader-dom-event.js

66 ms

connection-min.js

138 ms

vbulletin-core.js

266 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 90% of them (55 requests) were addressed to the original Classicshoptalk.com, 3% (2 requests) were made to Ssl.google-analytics.com and 3% (2 requests) were made to Classicperform.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Classicshoptalk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.0 kB (6%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classicshoptalk.com main page is 2.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. 35% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.5 kB

  • Original 53.2 kB
  • After minification 48.8 kB
  • After compression 9.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 43.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 46.2 kB

  • Original 2.1 MB
  • After minification 2.0 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. Classic Shop Talk images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 41.1 kB

  • Original 138.1 kB
  • After minification 138.1 kB
  • After compression 96.9 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 41.1 kB or 30% of the original size.

CSS Optimization

-40%

Potential reduce by 15.2 kB

  • Original 37.6 kB
  • After minification 37.6 kB
  • After compression 22.4 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. Classicshoptalk.com needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 40% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

classicshoptalk.com

classicshoptalk.com

199 ms

www.classicshoptalk.com

www.classicshoptalk.com

1955 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

66 ms

connection-min.js

connection-min.js

138 ms

vbulletin-core.js

vbulletin-core.js

266 ms

css.php

css.php

451 ms

css.php

css.php

391 ms

vbulletin_overlay.js

vbulletin_overlay.js

201 ms

vbulletin_cms.js

vbulletin_cms.js

202 ms

vbulletin_ajax_htmlloader.js

vbulletin_ajax_htmlloader.js

202 ms

css.php

css.php

445 ms

css.php

css.php

449 ms

vbulletin_md5.js

vbulletin_md5.js

268 ms

load.php

load.php

345 ms

vbulletin_lightbox.js

vbulletin_lightbox.js

332 ms

ga.js

ga.js

27 ms

SEMA.gif

SEMA.gif

100 ms

HeaderBackground.jpg

HeaderBackground.jpg

65 ms

HeaderLogo.jpg

HeaderLogo.jpg

130 ms

search.png

search.png

67 ms

navbit-home.png

navbit-home.png

66 ms

attachment.php

attachment.php

472 ms

attachment.php

attachment.php

395 ms

attachment.php

attachment.php

365 ms

attachment.php

attachment.php

542 ms

attachment.php

attachment.php

479 ms

attachment.php

attachment.php

553 ms

attachment.php

attachment.php

593 ms

attachment.php

attachment.php

793 ms

attachment.php

attachment.php

860 ms

attachment.php

attachment.php

770 ms

attachment.php

attachment.php

798 ms

attachment.php

attachment.php

931 ms

attachment.php

attachment.php

869 ms

attachment.php

attachment.php

1017 ms

attachment.php

attachment.php

1048 ms

rss_40b.png

rss_40b.png

863 ms

attachment.php

attachment.php

1186 ms

read_more_button.jpg

read_more_button.jpg

927 ms

attachment.php

attachment.php

1233 ms

attachment.php

attachment.php

1246 ms

attachment.php

attachment.php

1276 ms

attachment.php

attachment.php

1343 ms

attachment.php

attachment.php

1613 ms

attachment.php

attachment.php

1559 ms

cron.php

cron.php

1451 ms

CategoryBackground.jpg

CategoryBackground.jpg

1293 ms

navbit-arrow-right.png

navbit-arrow-right.png

1319 ms

treeview-min.js

treeview-min.js

1358 ms

treeview.css

treeview.css

1384 ms

__utm.gif

__utm.gif

11 ms

SEMA.gif

SEMA.gif

133 ms

poll.php

poll.php

76 ms

analytics.js

analytics.js

23 ms

top-highlight.png

top-highlight.png

66 ms

gradient-black-down.png

gradient-black-down.png

72 ms

plus-off.png

plus-off.png

72 ms

CategoryBackground4.jpg

CategoryBackground4.jpg

126 ms

collect

collect

13 ms

1955-Ford-LaTosca.jpg

1955-Ford-LaTosca.jpg

128 ms

1955-Ford-LaTosca.jpg

1955-Ford-LaTosca.jpg

68 ms

Accessibility Review

classicshoptalk.com accessibility score

50

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

[id] attributes on active, focusable elements are not unique

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

Best Practices

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

classicshoptalk.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 Classicshoptalk.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 Classicshoptalk.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

classicshoptalk.com

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