Tools & Wizards About Us
polycase.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

polycase.com

Plastic Enclosures & Boxes for the Electronics Industry

Page Load Speed

4.5 sec in total

First Response

189 ms

Resources Loaded

4 sec

Page Rendered

266 ms

polycase.com screenshot

About Website

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

Polycase is a premier manufacturer of plastic electronic enclosures and boxes. Purchase high-quality plastic, aluminum, steel and NEMA-rated enclosures for any application from Polycase.com.

Visit polycase.com

Key Findings

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

Performance Metrics

polycase.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value5,810 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

polycase.com

189 ms

www.polycase.com

814 ms

font.css

190 ms

master.css

196 ms

font-awesome.min.css

192 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 86% of them (114 requests) were addressed to the original Polycase.com, 5% (7 requests) were made to Server.iad.liveperson.net and 4% (5 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Polycase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 574.9 kB (43%)

Content Size

1.3 MB

After Optimization

763.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 108.6 kB

  • Original 123.4 kB
  • After minification 95.8 kB
  • After compression 14.7 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. This page needs HTML code to be minified as it can gain 27.6 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 108.6 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 58.7 kB

  • Original 563.2 kB
  • After minification 504.5 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. Polycase images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 342.9 kB

  • Original 566.0 kB
  • After minification 523.3 kB
  • After compression 223.2 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 342.9 kB or 61% of the original size.

CSS Optimization

-76%

Potential reduce by 64.7 kB

  • Original 85.5 kB
  • After minification 70.8 kB
  • After compression 20.8 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. Polycase.com needs all CSS files to be minified and compressed as it can save up to 64.7 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (32%)

Requests Now

131

After Optimization

89

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

polycase.com

polycase.com

189 ms

www.polycase.com

www.polycase.com

814 ms

font.css

font.css

190 ms

master.css

master.css

196 ms

font-awesome.min.css

font-awesome.min.css

192 ms

LightFace.css

LightFace.css

198 ms

home.css

home.css

200 ms

spin.css

spin.css

228 ms

css.css

css.css

317 ms

core.js

core.js

393 ms

more.js

more.js

419 ms

master.js

master.js

352 ms

LightFace.js

LightFace.js

351 ms

LightFace.Static.js

LightFace.Static.js

350 ms

googleanalyticsadvanced.js

googleanalyticsadvanced.js

415 ms

index-more.js

index-more.js

444 ms

js.js

js.js

447 ms

spin.js

spin.js

457 ms

mediabox.js

mediabox.js

478 ms

mediaboxAdvHomeTool.css

mediaboxAdvHomeTool.css

496 ms

element.js

element.js

49 ms

bg-body-grad.jpg

bg-body-grad.jpg

51 ms

bg-content-top2.png

bg-content-top2.png

181 ms

logo.png

logo.png

113 ms

bg-creditcards.gif

bg-creditcards.gif

181 ms

top-view-cart-btn.gif

top-view-cart-btn.gif

114 ms

btn-go.gif

btn-go.gif

112 ms

288561442505567.jpg

288561442505567.jpg

414 ms

280091442861520.jpg

280091442861520.jpg

467 ms

293211442505552.jpg

293211442505552.jpg

586 ms

295861441993601.jpg

295861441993601.jpg

464 ms

159501387383000.png

159501387383000.png

330 ms

241281295467172.jpg

241281295467172.jpg

232 ms

292181292007775.jpg

292181292007775.jpg

450 ms

40081389981759.jpg

40081389981759.jpg

512 ms

142721450725358.jpg

142721450725358.jpg

606 ms

89261366138516.jpg

89261366138516.jpg

632 ms

87721366138376.jpg

87721366138376.jpg

641 ms

83851366138441.jpg

83851366138441.jpg

659 ms

303001447685145.jpg

303001447685145.jpg

701 ms

287571447684967.jpg

287571447684967.jpg

753 ms

133871292007797.jpg

133871292007797.jpg

771 ms

61541389886597.jpg

61541389886597.jpg

824 ms

214161295467236.jpg

214161295467236.jpg

826 ms

254111388764839.jpg

254111388764839.jpg

841 ms

55771430493077.jpg

55771430493077.jpg

851 ms

238811295467284.jpg

238811295467284.jpg

901 ms

48381292007937.jpg

48381292007937.jpg

903 ms

262381292007955.jpg

262381292007955.jpg

922 ms

134051292007973.jpg

134051292007973.jpg

921 ms

325391441996445.jpg

325391441996445.jpg

931 ms

new.png

new.png

940 ms

317581441995433.jpg

317581441995433.jpg

983 ms

288361454613382.jpg

288361454613382.jpg

986 ms

89411351273462.jpg

89411351273462.jpg

1001 ms

214231389971320.jpg

214231389971320.jpg

1006 ms

tag.js

tag.js

62 ms

translateelement.css

translateelement.css

70 ms

main.js

main.js

102 ms

142731389968910.jpg

142731389968910.jpg

1000 ms

133861292008842.jpg

133861292008842.jpg

984 ms

ga.js

ga.js

30 ms

.jsonp

.jsonp

86 ms

292181292009087.jpg

292181292009087.jpg

957 ms

82171293119702.jpg

82171293119702.jpg

1012 ms

element_main.js

element_main.js

67 ms

205021332867821.jpg

205021332867821.jpg

978 ms

__utm.gif

__utm.gif

33 ms

67681296594988.jpg

67681296594988.jpg

917 ms

206621332867867.jpg

206621332867867.jpg

921 ms

translate_24dp.png

translate_24dp.png

76 ms

l

l

40 ms

cleardot.gif

cleardot.gif

62 ms

mTag.js

mTag.js

103 ms

262441292005838.jpg

262441292005838.jpg

889 ms

te_ctrl3.gif

te_ctrl3.gif

11 ms

134101292008805.jpg

134101292008805.jpg

814 ms

18 ms

29 ms

7 ms

8 ms

7 ms

9 ms

262381292008817.jpg

262381292008817.jpg

770 ms

110081292009753.jpg

110081292009753.jpg

753 ms

219701332868809.jpg

219701332868809.jpg

740 ms

11551406903256.jpg

11551406903256.jpg

802 ms

264381289995950.jpg

264381289995950.jpg

762 ms

48381292009858.jpg

48381292009858.jpg

751 ms

143331295019478.png

143331295019478.png

898 ms

17051445968559.JPG

17051445968559.JPG

792 ms

273261454535067.jpg

273261454535067.jpg

786 ms

305081390587901.png

305081390587901.png

922 ms

157381408561054.jpg

157381408561054.jpg

798 ms

193701406228453.jpg

193701406228453.jpg

872 ms

88031445974461.JPG

88031445974461.JPG

850 ms

104451367347200.jpg

104451367347200.jpg

804 ms

62081292511223.jpg

62081292511223.jpg

852 ms

158611295361148.jpg

158611295361148.jpg

840 ms

74621362752243.png

74621362752243.png

910 ms

159351371586490.png

159351371586490.png

898 ms

143161295032057.jpg

143161295032057.jpg

897 ms

142991295032187.jpg

142991295032187.jpg

883 ms

238741334781074.JPG

238741334781074.JPG

916 ms

175221295361214.png

175221295361214.png

912 ms

175721295361273.jpg

175721295361273.jpg

940 ms

257751295036789.jpg

257751295036789.jpg

931 ms

bg-main-nav-home.png

bg-main-nav-home.png

932 ms

bg-main-nav-about-us.png

bg-main-nav-about-us.png

916 ms

bg-main-nav-faq.png

bg-main-nav-faq.png

916 ms

bg-main-nav-shipping-information.png

bg-main-nav-shipping-information.png

911 ms

bg-main-nav-video-library.png

bg-main-nav-video-library.png

935 ms

bg-main-nav-view-by-series.png

bg-main-nav-view-by-series.png

922 ms

bg-main-nav.png

bg-main-nav.png

907 ms

bg-main-nav-customize-enclosures.png

bg-main-nav-customize-enclosures.png

902 ms

bg-main-nav-quote.png

bg-main-nav-quote.png

903 ms

bg-content.png

bg-content.png

962 ms

bg-product-nav-li.png

bg-product-nav-li.png

927 ms

bg-content-grad.png

bg-content-grad.png

927 ms

bg-prod-list-border.png

bg-prod-list-border.png

908 ms

surface-mount.png

surface-mount.png

888 ms

slide-controls.png

slide-controls.png

890 ms

waterproof.png

waterproof.png

870 ms

hinged.png

hinged.png

896 ms

desktop.png

desktop.png

845 ms

handheld-key-fob.png

handheld-key-fob.png

775 ms

potting-box.png

potting-box.png

775 ms

universal-use.png

universal-use.png

712 ms

wall-plug.png

wall-plug.png

825 ms

specialty.png

specialty.png

802 ms

accessories.png

accessories.png

774 ms

bg-footer.png

bg-footer.png

801 ms

print.css

print.css

121 ms

Accessibility Review

polycase.com accessibility score

61

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

ARIA IDs are not unique

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

polycase.com best practices score

67

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

polycase.com SEO score

81

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

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

polycase.com

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