Tools & Wizards About Us
classictruss.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

classictruss.com

Home Page | Home Page - Classic Truss

Page Load Speed

1.6 sec in total

First Response

91 ms

Resources Loaded

1.1 sec

Page Rendered

433 ms

classictruss.com screenshot

About Website

Click here to check amazing Classic Truss content. Otherwise, check out these important facts you probably never knew about classictruss.com

Visit classictruss.com

Key Findings

We analyzed Classictruss.com page load time and found that the first response time was 91 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

classictruss.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,950 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.246

50/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

classictruss.com

91 ms

classictruss.com

101 ms

js

66 ms

style.min.css

109 ms

styles.css

124 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 86% of them (42 requests) were addressed to the original Classictruss.com, 4% (2 requests) were made to Maxcdn.bootstrapcdn.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Classictruss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.9 kB (3%)

Content Size

1.5 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classictruss.com main page is 1.5 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 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 30.9 kB

  • Original 40.0 kB
  • After minification 35.5 kB
  • After compression 9.1 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 4.5 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 30.9 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.0 MB
  • After minification 1.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 Truss images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 13.7 kB

  • Original 390.8 kB
  • After minification 390.8 kB
  • After compression 377.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 2.3 kB

  • Original 67.1 kB
  • After minification 67.0 kB
  • After compression 64.8 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. Classictruss.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (67%)

Requests Now

45

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

classictruss.com

classictruss.com

91 ms

classictruss.com

classictruss.com

101 ms

js

js

66 ms

style.min.css

style.min.css

109 ms

styles.css

styles.css

124 ms

select2.css

select2.css

104 ms

front.css

front.css

146 ms

font-awesome.min.css

font-awesome.min.css

83 ms

bootstrap.min.css

bootstrap.min.css

111 ms

bootstrap-icons.css

bootstrap-icons.css

118 ms

swiper-bundle.min.css

swiper-bundle.min.css

196 ms

style.css

style.css

217 ms

responsive.css

responsive.css

193 ms

style.css

style.css

244 ms

jquery.min.js

jquery.min.js

228 ms

jquery-migrate.min.js

jquery-migrate.min.js

248 ms

jquery.min.js

jquery.min.js

42 ms

hooks.min.js

hooks.min.js

283 ms

i18n.min.js

i18n.min.js

284 ms

index.js

index.js

309 ms

index.js

index.js

322 ms

front.js

front.js

331 ms

select2.js

select2.js

359 ms

slick.js

slick.js

370 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

382 ms

swiper-bundle.min.js

swiper-bundle.min.js

425 ms

main.js

main.js

428 ms

api.js

api.js

48 ms

wp-polyfill.min.js

wp-polyfill.min.js

424 ms

index.js

index.js

489 ms

fonts.css

fonts.css

288 ms

variable.css

variable.css

300 ms

css2

css2

29 ms

phone-icon.png

phone-icon.png

44 ms

logo.png

logo.png

104 ms

white-logo.png

white-logo.png

99 ms

Why-Trusses-and-Wall-Panels-2.jpg

Why-Trusses-and-Wall-Panels-2.jpg

122 ms

our-servicevg.jpg

our-servicevg.jpg

99 ms

IMG_0885-scaled.jpg

IMG_0885-scaled.jpg

137 ms

text.jpg

text.jpg

158 ms

sponsor5.jpg

sponsor5.jpg

175 ms

sponsor4.jpg

sponsor4.jpg

183 ms

sponsor3.jpg

sponsor3.jpg

194 ms

sponsor2.jpg

sponsor2.jpg

212 ms

sponsor1.jpg

sponsor1.jpg

225 ms

footerbg.jpg

footerbg.jpg

239 ms

recaptcha__en.js

recaptcha__en.js

25 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

15 ms

bootstrap-icons.woff

bootstrap-icons.woff

251 ms

Accessibility Review

classictruss.com accessibility score

88

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

classictruss.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Page has valid source maps

SEO Factors

classictruss.com SEO score

81

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

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classictruss.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 Classictruss.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.

Social Sharing Optimization

classictruss.com

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