Tools & Wizards About Us
lumber2.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

lumber2.com

Page Load Speed

1.9 sec in total

First Response

362 ms

Resources Loaded

1.3 sec

Page Rendered

248 ms

lumber2.com screenshot

About Website

Visit lumber2.com now to see the best up-to-date Lumber 2 content for United States and also check out these interesting facts you probably never knew about lumber2.com

Your source for fence, lumber, Oklahoma barn kits, livestock feed, horse tack, hay, Carhartt and lawn and garden supplies.

Visit lumber2.com

Key Findings

We analyzed Lumber2.com page load time and found that the first response time was 362 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

lumber2.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value4.1 s

87/100

10%

Network Requests Diagram

Default.asp

362 ms

jquery.min.js

34 ms

jquery-ui.min.js

57 ms

jquery-ui.css

74 ms

default.css

123 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 85% of them (44 requests) were addressed to the original Lumber2.com, 6% (3 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Verify.authorize.net. The less responsive or slowest element that took the longest time to load (454 ms) belongs to the original domain Lumber2.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.2 kB (31%)

Content Size

359.3 kB

After Optimization

249.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 25.3 kB

  • Original 34.5 kB
  • After minification 32.4 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. 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 25.3 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 11.7 kB

  • Original 191.6 kB
  • After minification 180.0 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. Lumber 2 images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 57.1 kB

  • Original 113.2 kB
  • After minification 92.4 kB
  • After compression 56.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 57.1 kB or 50% of the original size.

CSS Optimization

-80%

Potential reduce by 16.1 kB

  • Original 20.0 kB
  • After minification 15.5 kB
  • After compression 3.9 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. Lumber2.com needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (45%)

Requests Now

51

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Default.asp

Default.asp

362 ms

jquery.min.js

jquery.min.js

34 ms

jquery-ui.min.js

jquery-ui.min.js

57 ms

jquery-ui.css

jquery-ui.css

74 ms

default.css

default.css

123 ms

volusion.js

volusion.js

131 ms

soft_add.js

soft_add.js

202 ms

soft_add.css

soft_add.css

132 ms

soft_add_mult.js

soft_add_mult.js

132 ms

javascripts.js

javascripts.js

204 ms

Imports.css

Imports.css

186 ms

seal.js

seal.js

32 ms

Colors.css

Colors.css

68 ms

Content_Area.css

Content_Area.css

69 ms

Template.css

Template.css

70 ms

Navigation.css

Navigation.css

69 ms

bgr1.jpg

bgr1.jpg

84 ms

header_bg.gif

header_bg.gif

87 ms

header.gif

header.gif

231 ms

arrow.gif

arrow.gif

84 ms

btn_go.gif

btn_go.gif

84 ms

content_tile.gif

content_tile.gif

85 ms

menu_top.gif

menu_top.gif

131 ms

menu_cap.gif

menu_cap.gif

132 ms

twitter%20follow.gif

twitter%20follow.gif

133 ms

cc_logo1.gif

cc_logo1.gif

135 ms

seal_volusion1.png

seal_volusion1.png

194 ms

Deer-Plot-Management.jpg

Deer-Plot-Management.jpg

385 ms

lumber.jpg

lumber.jpg

197 ms

treated-posts.jpg

treated-posts.jpg

199 ms

landscape-timbers.jpg

landscape-timbers.jpg

198 ms

cattle-panels.jpg

cattle-panels.jpg

260 ms

barbed-wire-fence.jpg

barbed-wire-fence.jpg

261 ms

t-posts.jpg

t-posts.jpg

262 ms

cedar-split-rail.jpg

cedar-split-rail.jpg

263 ms

post-and-rail-fence.jpg

post-and-rail-fence.jpg

292 ms

stockade-fence.jpg

stockade-fence.jpg

325 ms

blank.gif

blank.gif

327 ms

Load-N-Go-Free%20Service.gif

Load-N-Go-Free%20Service.gif

391 ms

carhartt-holiday-free-shipping.png

carhartt-holiday-free-shipping.png

327 ms

muck-boots-on-sale-and-free-shipping.png

muck-boots-on-sale-and-free-shipping.png

357 ms

chain-harrow-for-sale.jpg

chain-harrow-for-sale.jpg

454 ms

acct_top.gif

acct_top.gif

365 ms

create.gif

create.gif

364 ms

signin.gif

signin.gif

394 ms

submit.gif

submit.gif

416 ms

acct_cap.gif

acct_cap.gif

427 ms

secure90x72.gif

secure90x72.gif

11 ms

footer_background.gif

footer_background.gif

416 ms

ga.js

ga.js

11 ms

__utm.gif

__utm.gif

12 ms

roundtrip.js

roundtrip.js

9 ms

Accessibility Review

lumber2.com accessibility score

86

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

lumber2.com best practices score

92

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

Page has valid source maps

SEO Factors

lumber2.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lumber2.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lumber2.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

lumber2.com

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