Access qatarcanadian.com. Qatar Canadian Co. Green Environment and services of Landscaping & Garden Decoration

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value53.6 s

0/100

25%

SI (Speed Index)

Value33.5 s

0/100

10%

TBT (Total Blocking Time)

Value12,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.534

14/100

15%

TTI (Time to Interactive)

Value59.2 s

0/100

10%

qatarcanadian.com

183 ms

239 ms

189 ms

css

24 ms

css

40 ms

Our browser made a total of 161 requests to load all elements on the main page. We found that 60% of them (96 requests) were addressed to the original Qatarcanadian.com, 17% (28 requests) were made to Youtube.com and 11% (18 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Qatarcanadian.com.

Content Size

4.8 MB

After Optimization

4.7 MB

In fact, the total size of Qatarcanadian.com main page is 4.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. Only a small number of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 75.7 kB

Original 92.7 kB
After minification 92.3 kB
After compression 17.0 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 75.7 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 456 B

Original 4.1 MB
After minification 4.1 MB

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. Qatar Canadian images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 6.5 kB

Original 547.8 kB
After minification 547.7 kB
After compression 541.4 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

-0%

Potential reduce by 68 B

Original 68.1 kB
After minification 68.1 kB
After compression 68.0 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. Qatarcanadian.com has all CSS files already compressed.

Requests Now

136

After Optimization

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

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

button, link, and menuitem elements do not have accessible names.

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

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

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