Tools & Wizards About Us
empiresafety.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

empiresafety.com

Protective Equipment & Supplies | Empire Safety & Supply

Page Load Speed

3.3 sec in total

First Response

388 ms

Resources Loaded

2.7 sec

Page Rendered

176 ms

empiresafety.com screenshot

About Website

Click here to check amazing Empire Safety content. Otherwise, check out these important facts you probably never knew about empiresafety.com

Empire Safety & Supply has over 50 years experience providing clients with Safety, Hazmat, Industrial, and Controlled Environment needs.

Visit empiresafety.com

Key Findings

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

Performance Metrics

empiresafety.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value35.1 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.155

74/100

15%

TTI (Time to Interactive)

Value28.2 s

0/100

10%

Network Requests Diagram

www.empiresafety.com

388 ms

calendar.css

22 ms

styles-m.css

55 ms

bootstrap-grid.min.css

29 ms

photoswipe.css

28 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 61% of them (33 requests) were addressed to the original Empiresafety.com, 30% (16 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (980 ms) belongs to the original domain Empiresafety.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.6 kB (24%)

Content Size

905.5 kB

After Optimization

687.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 169.0 kB

  • Original 197.5 kB
  • After minification 189.4 kB
  • After compression 28.5 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 169.0 kB or 86% of the original size.

Image Optimization

-7%

Potential reduce by 45.4 kB

  • Original 639.2 kB
  • After minification 593.8 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. Empire Safety images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 99 B

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 11.5 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

-5%

Potential reduce by 3.0 kB

  • Original 57.2 kB
  • After minification 55.2 kB
  • After compression 54.1 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. Empiresafety.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (39%)

Requests Now

28

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.empiresafety.com

www.empiresafety.com

388 ms

calendar.css

calendar.css

22 ms

styles-m.css

styles-m.css

55 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

29 ms

photoswipe.css

photoswipe.css

28 ms

amslick.min.css

amslick.min.css

26 ms

owl.carousel.css

owl.carousel.css

34 ms

perfect-scrollbar.min.css

perfect-scrollbar.min.css

39 ms

swiper.min.css

swiper.min.css

42 ms

styles-l.css

styles-l.css

46 ms

css

css

31 ms

all.css

all.css

145 ms

logo.png

logo.png

79 ms

logo_1.png

logo_1.png

79 ms

spacer.gif

spacer.gif

399 ms

rocket-loader.min.js

rocket-loader.min.js

4 ms

preloader-img.svg

preloader-img.svg

13 ms

1150_440.png

1150_440.png

346 ms

575_220.png

575_220.png

385 ms

dark.jpg

dark.jpg

546 ms

Eye_Protection.png

Eye_Protection.png

408 ms

Respiratory.png

Respiratory.png

424 ms

Hand_Protection.png

Hand_Protection.png

417 ms

Fall_Protection.png

Fall_Protection.png

658 ms

Confined.png

Confined.png

632 ms

Shower_Wash.png

Shower_Wash.png

713 ms

Hearing.png

Hearing.png

848 ms

Hazardous_Storage.png

Hazardous_Storage.png

830 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

23 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

37 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

50 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

5 ms

opensans-400.woff

opensans-400.woff

646 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

30 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

5 ms

opensans-300.woff

opensans-300.woff

860 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

29 ms

opensans-600.woff

opensans-600.woff

874 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

29 ms

opensans-700.woff

opensans-700.woff

620 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

41 ms

opensans-800.woff

opensans-800.woff

980 ms

fa-solid-900.woff

fa-solid-900.woff

88 ms

fa-regular-400.woff

fa-regular-400.woff

123 ms

athlete2.woff

athlete2.woff

980 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

43 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

43 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

41 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

41 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

41 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

43 ms

print.css

print.css

374 ms

require.js

require.js

351 ms

Accessibility Review

empiresafety.com accessibility score

81

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

Image elements do not have [alt] attributes

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

empiresafety.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

empiresafety.com SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

empiresafety.com

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