Tools & Wizards About Us
hloeb.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

hloeb.com

Die Cutting, CNC Machining & Fabrication Services from H. Loeb

Page Load Speed

1.4 sec in total

First Response

281 ms

Resources Loaded

978 ms

Page Rendered

159 ms

hloeb.com screenshot

About Website

Welcome to hloeb.com homepage info - get ready to check H Loeb best content right away, or after learning these important things about hloeb.com

Since 1948 customers have relied on to deliver exceptional services, including die cutting, specialty laminating and CNC cutting or routing. We also offer custom thermal insulation!

Visit hloeb.com

Key Findings

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

Performance Metrics

hloeb.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value3,620 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

www.hloeb.com

281 ms

autoptimize_d749d86f1cfa8aa2407e60d7cdc99821.css

131 ms

dashicons.min.css

285 ms

css

54 ms

jquery.min.js

274 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 50% of them (14 requests) were addressed to the original Hloeb.com, 11% (3 requests) were made to Fonts.googleapis.com and 11% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (352 ms) belongs to the original domain Hloeb.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.9 kB (5%)

Content Size

906.5 kB

After Optimization

860.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 40.5 kB

  • Original 52.5 kB
  • After minification 52.5 kB
  • After compression 11.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 40.5 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 2.9 kB

  • Original 397.8 kB
  • After minification 394.9 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. H Loeb images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.0 kB

  • Original 376.7 kB
  • After minification 376.6 kB
  • After compression 374.7 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

-1%

Potential reduce by 508 B

  • Original 79.5 kB
  • After minification 79.5 kB
  • After compression 79.0 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. Hloeb.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (65%)

Requests Now

23

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of H Loeb. 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 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.hloeb.com

www.hloeb.com

281 ms

autoptimize_d749d86f1cfa8aa2407e60d7cdc99821.css

autoptimize_d749d86f1cfa8aa2407e60d7cdc99821.css

131 ms

dashicons.min.css

dashicons.min.css

285 ms

css

css

54 ms

jquery.min.js

jquery.min.js

274 ms

font-awesome.min.css

font-awesome.min.css

69 ms

js

js

98 ms

css

css

73 ms

all.css

all.css

52 ms

t.js

t.js

51 ms

css

css

75 ms

jquery-ui.min.js

jquery-ui.min.js

48 ms

hooks.min.js

hooks.min.js

197 ms

i18n.min.js

i18n.min.js

189 ms

api.js

api.js

65 ms

wp-polyfill.min.js

wp-polyfill.min.js

203 ms

autoptimize_6c954d27fa0517e6dbfabe9763d46b91.js

autoptimize_6c954d27fa0517e6dbfabe9763d46b91.js

352 ms

logo-100.png

logo-100.png

86 ms

home_111819-scaled.jpg

home_111819-scaled.jpg

255 ms

logo-footer.png

logo-footer.png

86 ms

Slitting-Box-on-Service-page-1-e1549982902169.jpg

Slitting-Box-on-Service-page-1-e1549982902169.jpg

155 ms

schmliziger-3.jpg

schmliziger-3.jpg

191 ms

ceiling-14596-e1549381212499.jpg

ceiling-14596-e1549381212499.jpg

162 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

57 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

64 ms

fa-solid-900.woff

fa-solid-900.woff

41 ms

fa-regular-400.woff

fa-regular-400.woff

50 ms

recaptcha__en.js

recaptcha__en.js

39 ms

Accessibility Review

hloeb.com accessibility score

91

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

hloeb.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hloeb.com SEO score

100

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

    EN

  • Encoding

    UTF-8

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

hloeb.com

Open Graph data is detected on the main page of H Loeb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: