Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

Page Load Speed

2.2 sec in total

First Response

555 ms

Resources Loaded

1.5 sec

Page Rendered

177 ms

strictly.ca screenshot

About Website

Welcome to strictly.ca homepage info - get ready to check Strictly best content for India right away, or after learning these important things about strictly.ca

Another business website from Canada listed in the Strictly Canadian website directory. Directory with top businesses from every province in Canada.

Visit strictly.ca

Key Findings

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

Performance Metrics

strictly.ca performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value10,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

strictly.ca

555 ms

main.css

122 ms

ie8.css

138 ms

show_ads.js

8 ms

ga.js

47 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 63% of them (31 requests) were addressed to the original Strictly.ca, 10% (5 requests) were made to Pagead2.googlesyndication.com and 8% (4 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (747 ms) belongs to the original domain Strictly.ca.

Page Optimization Overview & Recommendations

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

Content Size

81.8 kB

After Optimization

56.3 kB

In fact, the total size of Strictly.ca main page is 81.8 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 32.3 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 13.7 kB

  • Original 18.9 kB
  • After minification 18.2 kB
  • After compression 5.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 13.7 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 130 B

  • Original 16.9 kB
  • After minification 16.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. Strictly images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 396 B

  • Original 32.3 kB
  • After minification 32.1 kB
  • After compression 31.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

-82%

Potential reduce by 11.3 kB

  • Original 13.7 kB
  • After minification 9.9 kB
  • After compression 2.4 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. Strictly.ca needs all CSS files to be minified and compressed as it can save up to 11.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (60%)

Requests Now

48

After Optimization

19

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

Accessibility Review

strictly.ca accessibility score

66

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

strictly.ca 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

SEO Factors

strictly.ca SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Strictly.ca can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Strictly.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 description is not detected on the main page of Strictly. 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: