Access weekenddrive.ca. weekenddrive.ca

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

89/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.236

53/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

weekenddrive.ca

321 ms

ww38.weekenddrive.ca

635 ms

js3.js

7 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 33% of them (1 request) were addressed to the original Weekenddrive.ca, 33% (1 request) were made to Ww38.weekenddrive.ca and 33% (1 request) were made to D38psrni17bvxu.cloudfront.net. The less responsive or slowest element that took the longest time to load (635 ms) relates to the external source Ww38.weekenddrive.ca.

Content Size

3.4 kB

After Optimization

1.6 kB

In fact, the total size of Weekenddrive.ca main page is 3.4 kB. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. HTML takes 2.3 kB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 1.1 kB

Original 2.3 kB
After minification 2.2 kB
After compression 1.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 1.1 kB or 48% of the original size.

JavaScript Optimization

-65%

Potential reduce by 716 B

Original 1.1 kB
After minification 939 B
After compression 380 B

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 716 B or 65% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

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

High

Page is blocked from indexing

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/).

High

Document doesn't use legible font sizes

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

weekenddrive.ca

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