Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

permadur.com

Permanent Plate Lifting Magnet, Material Handling Magnets, Sheet Handling Equipment

Page Load Speed

1.4 sec in total

First Response

177 ms

Resources Loaded

799 ms

Page Rendered

463 ms

About Website

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

For over 45 years, Permadur Industries has been recognized as an industry leader in providing superior quality Below the Hook Lifting Equipment

Visit permadur.com

Key Findings

We analyzed Permadur.com page load time and found that the first response time was 177 ms and then it took 1.3 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

permadur.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

permadur.com

177 ms

permadur.com

243 ms

base.css

64 ms

permadur-logo.webp

118 ms

permadurlogo2-1.webp

158 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 93% of them (25 requests) were addressed to the original Permadur.com, 7% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (369 ms) belongs to the original domain Permadur.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.2 kB (26%)

Content Size

73.6 kB

After Optimization

54.4 kB

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

HTML Optimization

-80%

Potential reduce by 17.8 kB

  • Original 22.3 kB
  • After minification 17.7 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 21% 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 17.8 kB or 80% of the original size.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 37.9 kB
  • After minification 37.9 kB
  • After compression 37.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

-10%

Potential reduce by 1.4 kB

  • Original 13.4 kB
  • After minification 13.4 kB
  • After compression 12.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. Permadur.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Permadur. According to our analytics all requests are already optimized.

Accessibility Review

permadur.com accessibility score

95

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.

Best Practices

permadur.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

permadur.com SEO score

93

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

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

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