5.8 sec in total
79 ms
5.5 sec
226 ms
Click here to check amazing Maple Leaf content for Canada. Otherwise, check out these important facts you probably never knew about mapleleaf.com
We're bringing delicious, natural food to all Canadians. We only produce high-quality meats made with natural ingredients for a taste you and your family
Visit mapleleaf.comWe analyzed Mapleleaf.com page load time and found that the first response time was 79 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mapleleaf.com performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value7.2 s
5/100
25%
Value6.4 s
40/100
10%
Value880 ms
33/100
30%
Value0.008
100/100
15%
Value9.6 s
30/100
10%
79 ms
941 ms
339 ms
31 ms
43 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 31% of them (28 requests) were addressed to the original Mapleleaf.com, 36% (32 requests) were made to Static.xx.fbcdn.net and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Mapleleaf.com.
Page size can be reduced by 1.0 MB (31%)
3.3 MB
2.3 MB
In fact, the total size of Mapleleaf.com main page is 3.3 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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 26.7 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 26.7 kB or 80% of the original size.
Potential reduce by 627.1 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. Obviously, Maple Leaf needs image optimization as it can save up to 627.1 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 186.0 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 186.0 kB or 63% of the original size.
Potential reduce by 162.3 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. Mapleleaf.com needs all CSS files to be minified and compressed as it can save up to 162.3 kB or 84% of the original size.
Number of requests can be reduced by 48 (56%)
86
38
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maple Leaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
mapleleaf.com
79 ms
www.mapleleaf.com
941 ms
language-selector.css
339 ms
css
31 ms
css
43 ms
style.css
760 ms
style.css
52 ms
easy-columns.css
28 ms
platform.js
87 ms
jquery.min.js
44 ms
fastclick.js
7 ms
minified.js
1968 ms
sitepress.js
325 ms
analytics.js
92 ms
facebook-75x75.png
64 ms
youtube-75x75.png
65 ms
twitter-75x75.png
82 ms
pinterest-75x75.png
64 ms
logo.png
64 ms
arrow.png
921 ms
appehtite.png
64 ms
search.png
65 ms
menu-mobile.png
64 ms
search-mobile.png
65 ms
maple-leaf-top-dogs-original-wieners_483-160x125.jpg
65 ms
1031x527_FIF_rotator1.png
993 ms
externalicon-x2.png
65 ms
1031x527_brand_sites_in-store-offer.png
1075 ms
01.jpg
879 ms
Sustainability2013_v4.jpg
637 ms
menu-footer-x3.png
646 ms
desktop-v3-a.png
651 ms
externaliconblack-x2.png
657 ms
all.js
268 ms
collect
34 ms
113 ms
xd_arbiter.php
214 ms
xd_arbiter.php
417 ms
activityi;src=4468388;type=invmedia;cat=x8EDfEGq;ord=9275617769453.674
89 ms
ping
60 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
43 ms
fastbutton
117 ms
playpause.png
37 ms
postmessageRelay
34 ms
3193398744-postmessagerelay.js
61 ms
rpc:shindig_random.js
1108 ms
cb=gapi.loaded_0
30 ms
cb=gapi.loaded_1
31 ms
like_box.php
233 ms
IWXAbM4pe57.css
282 ms
QbOSWkfpDnM.css
351 ms
mJ3scex-8ho.css
420 ms
eXhc6OJ3pgj.css
567 ms
yYGNrWyPiTw.css
572 ms
j5kW2Ioz5M5.css
557 ms
UBsaA5Ft-O6.css
488 ms
FAHeNGXgPup.js
618 ms
FJmpeSpHpjS.js
633 ms
0wM5s1Khldu.js
570 ms
1bNoFZUdlYZ.js
643 ms
njO1TPvGzoR.js
645 ms
1QuX41zDRrx.js
646 ms
Oagsvfb4VWi.js
692 ms
m-2AbGY1fWh.js
884 ms
1FCa-btixu2.js
685 ms
IjqSyiwKeaX.js
695 ms
rBxSIHk4zIe.js
763 ms
pQrUxxo5oQp.js
758 ms
pXuoz98hZ0k.js
752 ms
b8XhdWI9eAN.js
759 ms
_UYztdBNTjs.js
759 ms
kvx5eeRG4FE.js
953 ms
Nn19HjwCsOL.js
825 ms
cb=gapi.loaded_0
11 ms
12717278_1282582905101982_2795204803932723127_n.png
420 ms
12717847_1282583028435303_8942048244037741818_n.png
480 ms
12729062_1257271794288217_833634583480444157_n.png
616 ms
245778_1290618194298453_1710382252_n.jpg
614 ms
12717278_1282582905101982_2795204803932723127_n.png
680 ms
12717675_1280572828636323_8010154457117294001_n.jpg
679 ms
wL6VQj7Ab77.png
84 ms
s7jcwEQH7Sx.png
83 ms
pimRBh7B6ER.png
82 ms
QDwYpIaRyfG.png
83 ms
l5aPruN9xMM.png
82 ms
K00K-UgnsKu.png
82 ms
K_65vAc89SX.png
68 ms
I6-MnjEovm5.js
69 ms
mapleleaf.com 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mapleleaf.com 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
mapleleaf.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mapleleaf.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 Mapleleaf.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.
mapleleaf.com
Open Graph description is not detected on the main page of Maple Leaf. 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: