Tools & Wizards About Us
pinders.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pinders.com

Pinder's Security Products - Experts in Electronics, Locksmithing and 24/7 Service

Page Load Speed

8.6 sec in total

First Response

2.2 sec

Resources Loaded

6 sec

Page Rendered

393 ms

pinders.com screenshot

About Website

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

Pinder’s Security Products for Hospitals, Residential, Industrial, & Educational Facilities. Clearance for the highest level of Canadian Military installations.

Visit pinders.com

Key Findings

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

Performance Metrics

pinders.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value11.1 s

5/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

www.pinders.com

2188 ms

ywraq-gutenberg.css

190 ms

style.css

212 ms

style.css

186 ms

woocommerce-layout.css

197 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 61% of them (40 requests) were addressed to the original Pinders.com, 27% (18 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Pinders.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.6 kB (31%)

Content Size

1.1 MB

After Optimization

795.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pinders.com main page is 1.1 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 425.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 328.6 kB

  • Original 379.0 kB
  • After minification 374.0 kB
  • After compression 50.4 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 328.6 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 17.2 kB

  • Original 271.3 kB
  • After minification 254.0 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. Pinder S images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 425.4 kB
  • After minification 425.4 kB
  • After compression 424.3 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

-7%

Potential reduce by 4.7 kB

  • Original 71.0 kB
  • After minification 70.8 kB
  • After compression 66.3 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. Pinders.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (84%)

Requests Now

43

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pinders.com

www.pinders.com

2188 ms

ywraq-gutenberg.css

ywraq-gutenberg.css

190 ms

style.css

style.css

212 ms

style.css

style.css

186 ms

woocommerce-layout.css

woocommerce-layout.css

197 ms

woocommerce.css

woocommerce.css

194 ms

style.min.css

style.min.css

179 ms

all.css

all.css

52 ms

ywraq-frontend.css

ywraq-frontend.css

212 ms

style.css

style.css

209 ms

v4-shims.css

v4-shims.css

65 ms

foxyshop.css

foxyshop.css

221 ms

jquery.min.js

jquery.min.js

243 ms

jquery-migrate.min.js

jquery-migrate.min.js

235 ms

rbtools.min.js

rbtools.min.js

360 ms

rs6.min.js

rs6.min.js

400 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

390 ms

js.cookie.min.js

js.cookie.min.js

396 ms

woocommerce.min.js

woocommerce.min.js

414 ms

js

js

79 ms

et-core-unified-229021.min.css

et-core-unified-229021.min.css

420 ms

email-decode.min.js

email-decode.min.js

370 ms

rbtools.min.js

rbtools.min.js

558 ms

rs6.min.js

rs6.min.js

587 ms

css

css

44 ms

wc-blocks.css

wc-blocks.css

571 ms

rs6.css

rs6.css

578 ms

sourcebuster.min.js

sourcebuster.min.js

583 ms

order-attribution.min.js

order-attribution.min.js

616 ms

scripts.min.js

scripts.min.js

743 ms

es6-promise.auto.min.js

es6-promise.auto.min.js

781 ms

api.js

api.js

42 ms

recaptcha.js

recaptcha.js

783 ms

jquery.fitvids.js

jquery.fitvids.js

782 ms

frontend-bundle.min.js

frontend-bundle.min.js

784 ms

api.js

api.js

63 ms

frontend.min.js

frontend.min.js

673 ms

common.js

common.js

849 ms

Pinders-2022.png

Pinders-2022.png

700 ms

dummy.png

dummy.png

531 ms

logo_footer-300x74.png

logo_footer-300x74.png

576 ms

allmar_logo_footer_pinders_white.png

allmar_logo_footer_pinders_white.png

532 ms

fa-solid-900.ttf

fa-solid-900.ttf

34 ms

fa-regular-400.ttf

fa-regular-400.ttf

30 ms

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

pxiByp8kv8JHgFVrLDz8Z1JlEw.woff

15 ms

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1JlEA.ttf

25 ms

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

pxiByp8kv8JHgFVrLFj_Z1JlEw.woff

30 ms

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1JlEA.ttf

34 ms

pxiGyp8kv8JHgFVrLPTufntG.woff

pxiGyp8kv8JHgFVrLPTufntG.woff

31 ms

pxiGyp8kv8JHgFVrLPTufntF.ttf

pxiGyp8kv8JHgFVrLPTufntF.ttf

32 ms

pxiEyp8kv8JHgFVrJJnedA.woff

pxiEyp8kv8JHgFVrJJnedA.woff

33 ms

pxiEyp8kv8JHgFVrJJnedw.ttf

pxiEyp8kv8JHgFVrJJnedw.ttf

32 ms

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

pxiByp8kv8JHgFVrLGT9Z1JlEw.woff

34 ms

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1JlEA.ttf

51 ms

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

pxiByp8kv8JHgFVrLEj6Z1JlEw.woff

52 ms

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1JlEA.ttf

51 ms

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

pxiByp8kv8JHgFVrLCz7Z1JlEw.woff

52 ms

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1JlEA.ttf

52 ms

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

pxiByp8kv8JHgFVrLDD4Z1JlEw.woff

52 ms

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1JlEA.ttf

52 ms

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

pxiByp8kv8JHgFVrLBT5Z1JlEw.woff

53 ms

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1JlEA.ttf

53 ms

modules.woff

modules.woff

620 ms

pinders-home-mid-bg-min.jpg

pinders-home-mid-bg-min.jpg

625 ms

home-mid-bg-image-pinders.png

home-mid-bg-image-pinders.png

1937 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

180 ms

Accessibility Review

pinders.com accessibility score

84

Accessibility Issues

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

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

pinders.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pinders.com SEO score

93

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

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

pinders.com

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