Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

pft.ca

Solutions PFT | intégration audiovisuelle | Montréal, Québec

Page Load Speed

822 ms in total

First Response

100 ms

Resources Loaded

643 ms

Page Rendered

79 ms

pft.ca screenshot

About Website

Visit pft.ca now to see the best up-to-date PFT content and also check out these interesting facts you probably never knew about pft.ca

Service de consultation et d'intégration de systèmes de communication, audiovisuelle et domotique. intégration audiovisuel |

Visit pft.ca

Key Findings

We analyzed Pft.ca page load time and found that the first response time was 100 ms and then it took 722 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

pft.ca performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value990 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

pft.ca

100 ms

www.pft.ca

74 ms

bt

83 ms

require.min.js

52 ms

main-r.min.js

60 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Pft.ca, 74% (29 requests) were made to Static.parastorage.com and 15% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (257 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (77%)

Content Size

2.8 MB

After Optimization

657.1 kB

In fact, the total size of Pft.ca main page is 2.8 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. 65% of websites need less resources to load. Javascripts take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.6 kB

  • Original 42.8 kB
  • After minification 42.6 kB
  • After compression 9.2 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 33.6 kB or 79% of the original size.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.8 MB
  • After minification 2.7 MB
  • After compression 646.1 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 2.1 MB or 77% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Pft.ca needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (89%)

Requests Now

37

After Optimization

4

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

Accessibility Review

pft.ca accessibility score

90

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.

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

Best Practices

pft.ca best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

pft.ca SEO score

92

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

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

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pft.ca can be misinterpreted by Google and other search engines. Our service has detected that French 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 Pft.ca 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 data is detected on the main page of PFT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: