3.9 sec in total
402 ms
2.4 sec
1.2 sec
Click here to check amazing Amazing content for Canada. Otherwise, check out these important facts you probably never knew about amazing.ca
Search the world's information, including webpages, images, videos and more. Google has many special features to help you find exactly what you're looking for.
Visit amazing.caWe analyzed Amazing.ca page load time and found that the first response time was 402 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
amazing.ca performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value3.5 s
63/100
25%
Value4.4 s
73/100
10%
Value770 ms
38/100
30%
Value0.018
100/100
15%
Value7.5 s
47/100
10%
402 ms
319 ms
496 ms
168 ms
374 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 81% of them (54 requests) were addressed to the original Amazing.ca, 4% (3 requests) were made to S7.addthis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (993 ms) belongs to the original domain Amazing.ca.
Page size can be reduced by 1.5 MB (24%)
6.1 MB
4.6 MB
In fact, the total size of Amazing.ca main page is 6.1 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. 60% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 152.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 152.2 kB or 77% of the original size.
Potential reduce by 13.7 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. Amazing images are well optimized though.
Potential reduce by 967.5 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 967.5 kB or 72% of the original size.
Potential reduce by 331.9 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. Amazing.ca needs all CSS files to be minified and compressed as it can save up to 331.9 kB or 90% of the original size.
Number of requests can be reduced by 41 (64%)
64
23
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amazing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
amazing.ca
402 ms
84dcca2de9ecb9a893aa10754e7c6401.css
319 ms
prototype.js
496 ms
ccard.js
168 ms
validation.js
374 ms
builder.js
167 ms
effects.js
371 ms
dragdrop.js
371 ms
controls.js
412 ms
slider.js
395 ms
js.js
415 ms
form.js
417 ms
translate.js
416 ms
cookies.js
474 ms
window.js
655 ms
checkout.js
521 ms
jquery-1.7.2.min.js
662 ms
jquery-noconflict.js
521 ms
jquery.owlcarousel.min.js
557 ms
jquery.easing.min.js
568 ms
jquery.accordion.min.js
578 ms
searchautocomplete.js
578 ms
modernizr.custom.min.js
635 ms
matchMedia.js
638 ms
matchMedia.addListener.js
666 ms
enquire.js
666 ms
jquery.tabs.min.js
708 ms
imagesloaded.js
718 ms
app.js
726 ms
css
31 ms
styles.css
809 ms
addthis_widget.js
16 ms
analytics.js
122 ms
logo.gif
170 ms
Shamrocks.jpg
438 ms
1.png
210 ms
link-separator.png
209 ms
tall_pageant.jpg
436 ms
tall_easter.jpg
450 ms
tall_purim.jpg
330 ms
wide_starWarsVII.jpg
551 ms
wide_halloweenFamily.jpg
553 ms
1200x397_medieval.jpg
607 ms
wide_western.jpg
617 ms
1200x397_decades.jpg
626 ms
tall_luau.jpg
631 ms
tall_balloons.jpg
993 ms
tall_mardiGrasB.jpg
649 ms
1200x397_pinatas.jpg
782 ms
1200x397_petCostumes.jpg
794 ms
1200x397_balloonsv4.jpg
886 ms
1200x397_bachelorette2015.png
812 ms
1200x397_amazingBalloonsV2.jpg
827 ms
paymentlogos.png
864 ms
collect
15 ms
ThemeIcons.woff
825 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
12 ms
bullet.png
834 ms
dc.js
114 ms
300lo.json
64 ms
sh.8e5f85691f9aaa082472a194.html
85 ms
__utm.gif
191 ms
layers.e5ea973510bf60b3db41.js
7 ms
datapair
100 ms
99 ms
b26e2dd14e5d34f5ebee3de20fb23f7c.css
83 ms
nr-885.min.js
44 ms
amazing.ca accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
amazing.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
amazing.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amazing.ca 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 Amazing.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.
amazing.ca
Open Graph description is not detected on the main page of Amazing. 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: