Tools & Wizards About Us
lehmanpipe.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lehmanpipe.com

Lehman Pipe Supply | 70 years of Excellence and Still Counting

Page Load Speed

4.6 sec in total

First Response

917 ms

Resources Loaded

2.9 sec

Page Rendered

750 ms

lehmanpipe.com screenshot

About Website

Welcome to lehmanpipe.com homepage info - get ready to check Lehman Pipe best content right away, or after learning these important things about lehmanpipe.com

For over 70 years we have been a wholesaler of pipe, valves and fittings servicing the Mining, Power Generation, Water Technology, Agriculture, Municipal, Plumbing, Fire Protection, HVAC, Commercial &...

Visit lehmanpipe.com

Key Findings

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

Performance Metrics

lehmanpipe.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

lehmanpipe.com

917 ms

moss.min.css

101 ms

ngg-smart-image-search-public.css

155 ms

genericons.css

204 ms

fancybox.css

16 ms

Our browser made a total of 142 requests to load all elements on the main page. We found that 76% of them (108 requests) were addressed to the original Lehmanpipe.com, 20% (28 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (917 ms) belongs to the original domain Lehmanpipe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.1 kB (8%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lehmanpipe.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 161.4 kB

  • Original 191.2 kB
  • After minification 184.5 kB
  • After compression 29.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 161.4 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 14.0 kB

  • Original 1.5 MB
  • After minification 1.4 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. Lehman Pipe images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 4.0 kB

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

CSS Optimization

-4%

Potential reduce by 10.6 kB

  • Original 264.1 kB
  • After minification 263.7 kB
  • After compression 253.5 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. Lehmanpipe.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 81 (72%)

Requests Now

113

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lehmanpipe.com

lehmanpipe.com

917 ms

moss.min.css

moss.min.css

101 ms

ngg-smart-image-search-public.css

ngg-smart-image-search-public.css

155 ms

genericons.css

genericons.css

204 ms

fancybox.css

fancybox.css

16 ms

job-listings.css

job-listings.css

157 ms

frontend.min.css

frontend.min.css

158 ms

swiper.min.css

swiper.min.css

155 ms

e-swiper.min.css

e-swiper.min.css

153 ms

post-8.css

post-8.css

209 ms

frontend.min.css

frontend.min.css

317 ms

global.css

global.css

207 ms

post-18.css

post-18.css

213 ms

post-1914.css

post-1914.css

210 ms

post-1917.css

post-1917.css

258 ms

default.css

default.css

261 ms

style.css

style.css

260 ms

css2

css2

34 ms

bootstrap.min.css

bootstrap.min.css

327 ms

fontawesome.min.css

fontawesome.min.css

334 ms

magnific-popup.min.css

magnific-popup.min.css

311 ms

slick.min.css

slick.min.css

313 ms

style.css

style.css

425 ms

css

css

53 ms

smartslider.min.css

smartslider.min.css

370 ms

css

css

56 ms

jquery.min.js

jquery.min.js

372 ms

jquery-migrate.min.js

jquery-migrate.min.js

376 ms

ngg-smart-image-search-public.js

ngg-smart-image-search-public.js

379 ms

n2.min.js

n2.min.js

378 ms

smartslider-frontend.min.js

smartslider-frontend.min.js

494 ms

ss-simple.min.js

ss-simple.min.js

492 ms

widget-text-editor.min.css

widget-text-editor.min.css

490 ms

widget-social-icons.min.css

widget-social-icons.min.css

491 ms

apple-webkit.min.css

apple-webkit.min.css

492 ms

widget-icon-list.min.css

widget-icon-list.min.css

493 ms

widget-image.min.css

widget-image.min.css

493 ms

widget-divider.min.css

widget-divider.min.css

494 ms

widget-image-box.min.css

widget-image-box.min.css

493 ms

fancybox.umd.js

fancybox.umd.js

4 ms

post-4282.css

post-4282.css

499 ms

widget-spacer.min.css

widget-spacer.min.css

449 ms

widget-heading.min.css

widget-heading.min.css

394 ms

post-4333.css

post-4333.css

393 ms

post-4355.css

post-4355.css

393 ms

post-4385.css

post-4385.css

393 ms

widget-tabs.min.css

widget-tabs.min.css

553 ms

post-4407.css

post-4407.css

509 ms

post-4415.css

post-4415.css

504 ms

post-4417.css

post-4417.css

503 ms

post-4419.css

post-4419.css

503 ms

post-4658.css

post-4658.css

496 ms

post-4663.css

post-4663.css

516 ms

post-5622.css

post-5622.css

508 ms

rs6.css

rs6.css

510 ms

submit.js

submit.js

458 ms

moss.min.js

moss.min.js

456 ms

fancyapps-fancybind-v-5-0.js

fancyapps-fancybind-v-5-0.js

448 ms

plumer.ajax.js

plumer.ajax.js

498 ms

rbtools.min.js

rbtools.min.js

528 ms

rs6.min.js

rs6.min.js

543 ms

bootstrap.min.js

bootstrap.min.js

460 ms

circle-progress.js

circle-progress.js

457 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

460 ms

jquery-ui.min.js

jquery-ui.min.js

492 ms

jquery.counterup.min.js

jquery.counterup.min.js

484 ms

fa95f1f6a4a516ba7d705015d560e7b9.png

fa95f1f6a4a516ba7d705015d560e7b9.png

236 ms

slick.min.js

slick.min.js

371 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

372 ms

tilt.jquery.min.js

tilt.jquery.min.js

392 ms

imagesloaded.min.js

imagesloaded.min.js

395 ms

main.js

main.js

394 ms

jquery.sticky.min.js

jquery.sticky.min.js

398 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

405 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

403 ms

webpack.runtime.min.js

webpack.runtime.min.js

444 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

190 ms

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

4iCv6KVjbNBYlgoCjC3jsGyI.ttf

190 ms

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

4iCv6KVjbNBYlgoC1CzjsGyI.ttf

177 ms

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

4iCv6KVjbNBYlgoCxCvjsGyI.ttf

190 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk79FN_C-bw.ttf

190 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk7PFN_C-bw.ttf

190 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk6jFN_C-bw.ttf

192 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59FN_C-bw.ttf

192 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4jE9_C-bw.ttf

192 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk4aE9_C-bw.ttf

192 ms

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf

xn7_YHE41ni1AdIRqAuZuw1Bx9mbZk59E9_C-bw.ttf

193 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

191 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

208 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

207 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

208 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

207 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

208 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

192 ms

KFOkCnqEu92Fr1MmgWxP.ttf

KFOkCnqEu92Fr1MmgWxP.ttf

211 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

208 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

210 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

210 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

208 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

210 ms

frontend-modules.min.js

frontend-modules.min.js

446 ms

hooks.min.js

hooks.min.js

439 ms

i18n.min.js

i18n.min.js

447 ms

frontend.min.js

frontend.min.js

453 ms

core.min.js

core.min.js

450 ms

frontend.min.js

frontend.min.js

492 ms

elements-handlers.min.js

elements-handlers.min.js

480 ms

4iCu6KVjbNBYlgoKej70l0w.ttf

4iCu6KVjbNBYlgoKej70l0w.ttf

152 ms

4iCp6KVjbNBYlgoKejYHtFyPN4Q.ttf

4iCp6KVjbNBYlgoKejYHtFyPN4Q.ttf

151 ms

4iCp6KVjbNBYlgoKejZftVyPN4Q.ttf

4iCp6KVjbNBYlgoKejZftVyPN4Q.ttf

151 ms

4iCp6KVjbNBYlgoKejZPslyPN4Q.ttf

4iCp6KVjbNBYlgoKejZPslyPN4Q.ttf

151 ms

plumer-core.js

plumer-core.js

330 ms

plumer-frontend.js

plumer-frontend.js

340 ms

logo-min-1024x723.png

logo-min-1024x723.png

390 ms

image-3-1.png

image-3-1.png

394 ms

i-3.webp

i-3.webp

383 ms

image-9-1.png

image-9-1.png

384 ms

i-2.webp

i-2.webp

326 ms

image-8.png

image-8.png

333 ms

Untitled-1_4.jpg

Untitled-1_4.jpg

377 ms

oil-industry.png

oil-industry.png

376 ms

hydro-power-1.png

hydro-power-1.png

363 ms

plumbing.png

plumbing.png

325 ms

plumbing-1.png

plumbing-1.png

327 ms

mining-cart.png

mining-cart.png

325 ms

city.png

city.png

363 ms

hydro-power.png

hydro-power.png

363 ms

industry.png

industry.png

333 ms

plumber.png

plumber.png

300 ms

plumbing-2.png

plumbing-2.png

304 ms

neighborhood.png

neighborhood.png

303 ms

vehicle.png

vehicle.png

348 ms

HoldRiteLogo-2.png

HoldRiteLogo-2.png

331 ms

Milwaukee.png

Milwaukee.png

327 ms

Logo-Spears-Logo.png

Logo-Spears-Logo.png

327 ms

Victaulic.png

Victaulic.png

331 ms

Tylerlogo.png

Tylerlogo.png

329 ms

NIBCO.png

NIBCO.png

365 ms

Screenshot_from_2024-04-25_13-01-29-removebg-preview-removebg-preview.png

Screenshot_from_2024-04-25_13-01-29-removebg-preview-removebg-preview.png

366 ms

LPPS-building-min-1024x683.jpg

LPPS-building-min-1024x683.jpg

329 ms

image-39.png

image-39.png

480 ms

i-4.webp

i-4.webp

330 ms

Accessibility Review

lehmanpipe.com accessibility score

94

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

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

lehmanpipe.com SEO score

83

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

lehmanpipe.com

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