Access secure.macleans.ca. Macleans

name

value

score

weighting

FCP (First Contentful Paint)

Value19.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.6 s

0/100

25%

SI (Speed Index)

Value22.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.431

22/100

15%

TTI (Time to Interactive)

Value29.2 s

0/100

10%

secure.macleans.ca

179 ms

index.css

37 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Secure.macleans.ca and no external sources were called. The less responsive or slowest element that took the longest time to load (179 ms) belongs to the original domain Secure.macleans.ca.

Content Size

1.4 kB

After Optimization

746 B

In fact, the total size of Secure.macleans.ca main page is 1.4 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. CSS take 718 B which makes up the majority of the site volume.

HTML Optimization

-39%

Potential reduce by 255 B

Original 646 B
After minification 622 B
After compression 391 B

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

CSS Optimization

-51%

Potential reduce by 363 B

Original 718 B
After minification 665 B
After compression 355 B

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. Secure.macleans.ca needs all CSS files to be minified and compressed as it can save up to 363 B or 51% 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 Secure Macleans. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Secure.macleans.ca can be misinterpreted by Google and other search engines. Our service has detected that English 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 Secure.macleans.ca main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

secure.macleans.ca

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