Tools & Wizards About Us
tricolumber.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

tricolumber.com

Construction Materials, Lumber | Hughes Springs, TX - Trico Lumber Co.

Page Load Speed

1.7 sec in total

First Response

318 ms

Resources Loaded

1 sec

Page Rendered

341 ms

tricolumber.com screenshot

About Website

Visit tricolumber.com now to see the best up-to-date Trico Lumber content and also check out these interesting facts you probably never knew about tricolumber.com

Visit our Hughes Springs, TX, store for the construction materials you need to finish your project. We offer hardware, lumber, and more.

Visit tricolumber.com

Key Findings

We analyzed Tricolumber.com page load time and found that the first response time was 318 ms and then it took 1.3 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

tricolumber.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

tricolumber.com

318 ms

4c496dbb-f611-419d-b485-fb5b029491bf

157 ms

css2

42 ms

entry.rVHieY5q.css

41 ms

StoreLocatorContent.QH92lMVg.css

58 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 79% of them (27 requests) were addressed to the original Tricolumber.com, 12% (4 requests) were made to Cdn.builder.io and 3% (1 request) were made to App.termly.io. The less responsive or slowest element that took the longest time to load (414 ms) relates to the external source Cdn.builder.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.9 kB (34%)

Content Size

608.3 kB

After Optimization

403.4 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-81%

Potential reduce by 201.8 kB

  • Original 248.9 kB
  • After minification 245.3 kB
  • After compression 47.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. 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 201.8 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 348.4 kB
  • After minification 347.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. Trico Lumber images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 1.8 kB

  • Original 10.9 kB
  • After minification 10.9 kB
  • After compression 9.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.8 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (82%)

Requests Now

33

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tricolumber.com

tricolumber.com

318 ms

4c496dbb-f611-419d-b485-fb5b029491bf

4c496dbb-f611-419d-b485-fb5b029491bf

157 ms

css2

css2

42 ms

entry.rVHieY5q.css

entry.rVHieY5q.css

41 ms

StoreLocatorContent.QH92lMVg.css

StoreLocatorContent.QH92lMVg.css

58 ms

index.BAiCaAlX.css

index.BAiCaAlX.css

52 ms

index.BXx0OYIg.css

index.BXx0OYIg.css

63 ms

OrgillTransparentButton.C_RX_5ad.css

OrgillTransparentButton.C_RX_5ad.css

52 ms

DeprecatedSfPrice.DmEnd3WM.css

DeprecatedSfPrice.DmEnd3WM.css

67 ms

index.DVyCT8C6.css

index.DVyCT8C6.css

81 ms

GlobalBackToHome.D222QM1S.css

GlobalBackToHome.D222QM1S.css

82 ms

DeprecatedSfList.CEtTdQxD.css

DeprecatedSfList.CEtTdQxD.css

82 ms

ListPagination.D6CnZ0a9.css

ListPagination.D6CnZ0a9.css

91 ms

OrgillInput.BXSo8Y_6.css

OrgillInput.BXSo8Y_6.css

100 ms

OrgillSelect.BkVQRQwC.css

OrgillSelect.BkVQRQwC.css

103 ms

ShoppingListIcon.XfGFmGc0.css

ShoppingListIcon.XfGFmGc0.css

118 ms

OrgillModal.CW8wtmB-.css

OrgillModal.CW8wtmB-.css

114 ms

ConfirmationModal.D9Vek46N.css

ConfirmationModal.D9Vek46N.css

115 ms

OrgillLink.CZMBP4Fx.css

OrgillLink.CZMBP4Fx.css

129 ms

DeprecatedSfMenuItem.D4kEn8NR.css

DeprecatedSfMenuItem.D4kEn8NR.css

130 ms

DeprecatedSfNotification.CpF1PuZN.css

DeprecatedSfNotification.CpF1PuZN.css

135 ms

C5_vcf3d.js

C5_vcf3d.js

275 ms

emerge2_analytics_v3.js

emerge2_analytics_v3.js

132 ms

pixel

pixel

157 ms

assets%2F26221570817c4fa094668b1a84691c6e%2F818856268b25489ea3f29f2c7d325123

assets%2F26221570817c4fa094668b1a84691c6e%2F818856268b25489ea3f29f2c7d325123

37 ms

assets%2F26221570817c4fa094668b1a84691c6e%2F60dcc6b042fc41b1aadf25cc2546b7cd

assets%2F26221570817c4fa094668b1a84691c6e%2F60dcc6b042fc41b1aadf25cc2546b7cd

414 ms

assets%2F26221570817c4fa094668b1a84691c6e%2Fe3b40ed2792a47349f96bc933eead7dd

assets%2F26221570817c4fa094668b1a84691c6e%2Fe3b40ed2792a47349f96bc933eead7dd

229 ms

BZvUusuV.js

BZvUusuV.js

46 ms

CQWqm95k.js

CQWqm95k.js

40 ms

D_g9exR2.js

D_g9exR2.js

40 ms

C-QckzH5.js

C-QckzH5.js

41 ms

6qTV4sRH.js

6qTV4sRH.js

39 ms

Dv7GYW0O.js

Dv7GYW0O.js

38 ms

D67FAEJV.js

D67FAEJV.js

44 ms

Accessibility Review

tricolumber.com accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

tricolumber.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

tricolumber.com SEO score

92

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tricolumber.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tricolumber.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

tricolumber.com

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