17.2 sec in total
1.5 sec
14.9 sec
843 ms
Welcome to eatinscanada.com homepage info - get ready to check Eatinscanada best content for Canada right away, or after learning these important things about eatinscanada.com
Recipes, reviews, interviews and events. A blog about food.
Visit eatinscanada.comWe analyzed Eatinscanada.com page load time and found that the first response time was 1.5 sec and then it took 15.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
eatinscanada.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value8.8 s
1/100
25%
Value14.6 s
1/100
10%
Value550 ms
54/100
30%
Value0
100/100
15%
Value11.1 s
20/100
10%
1489 ms
482 ms
53 ms
276 ms
110 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 62% of them (63 requests) were addressed to the original Eatinscanada.com, 10% (10 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (12.1 sec) belongs to the original domain Eatinscanada.com.
Page size can be reduced by 704.1 kB (37%)
1.9 MB
1.2 MB
In fact, the total size of Eatinscanada.com main page is 1.9 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 927.2 kB which makes up the majority of the site volume.
Potential reduce by 56.9 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 56.9 kB or 78% of the original size.
Potential reduce by 14.5 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. Eatinscanada images are well optimized though.
Potential reduce by 411.6 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 411.6 kB or 68% of the original size.
Potential reduce by 221.1 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. Eatinscanada.com needs all CSS files to be minified and compressed as it can save up to 221.1 kB or 79% of the original size.
Number of requests can be reduced by 60 (67%)
89
29
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eatinscanada. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
eatinscanada.com
1489 ms
wp-emoji-release.min.js
482 ms
twentyfourteen.css
53 ms
public.css
276 ms
events_manager.css
110 ms
wprmenu.css
51 ms
css
27 ms
wpurp-public-forced.css
352 ms
css
47 ms
select2.css
131 ms
checkbox.min.css
149 ms
css
62 ms
genericons.css
469 ms
style.css
998 ms
style.css
311 ms
widgets.min.css
352 ms
form.min.css
390 ms
jetpack.css
924 ms
style.css
432 ms
style.css
1400 ms
jquery.js
2038 ms
jquery-migrate.min.js
518 ms
core.min.js
557 ms
widget.min.js
597 ms
position.min.js
637 ms
mouse.min.js
678 ms
sortable.min.js
834 ms
datepicker.min.js
992 ms
menu.min.js
1115 ms
autocomplete.min.js
961 ms
resizable.min.js
1781 ms
draggable.min.js
1354 ms
button.min.js
1241 ms
dialog.min.js
1124 ms
events-manager.js
1750 ms
jquery.transit.min.js
1277 ms
jquery.sidr.js
1317 ms
wprmenu.js
1357 ms
form.js
620 ms
public.js
659 ms
droppable.min.js
661 ms
suggest.min.js
661 ms
wpurp-public.js
1837 ms
devicepx-jetpack.js
7 ms
gprofiles.js
60 ms
wpgroho.js
681 ms
comment-reply.min.js
680 ms
masonry.min.js
1152 ms
jquery.masonry.min.js
721 ms
functions.js
762 ms
wp-embed.min.js
801 ms
sharing.js
920 ms
e-201611.js
9 ms
ga.js
28 ms
CurlingLeafLettuceFamilyFoods.jpg
12076 ms
EC_WP_Banner03.jpg
1357 ms
pattern-dark.svg
124 ms
EnriqueWalking-640x372.jpg
1366 ms
banana-coconut-upside-down-cake-21-664x372.jpg
1234 ms
A-winning-garden-672x372.jpg
1308 ms
first-tomato2-672x372.jpg
1139 ms
mulligatawny-672x372.jpg
1957 ms
BisqueCrawdads-copy-672x372.jpg
2144 ms
WeAreOne900-300x186.jpg
1426 ms
ThaiSoup02-300x196.jpg
2101 ms
EasyDateOvenBookCoverXsm.jpg
2246 ms
twitter.png
1466 ms
facebook.png
1510 ms
feed.png
1548 ms
widgets.js
58 ms
__utm.gif
65 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
127 ms
BTu4SsVveqk58cdYjlaM9g.ttf
127 ms
zpv3sOKAbMf4wff105oLjw.ttf
127 ms
5pEc4QKTMA2oB4Hi9NkS4w.ttf
189 ms
Genericons.svg
3182 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
57 ms
LgcV55siz7BRNdbO3Huj5g.ttf
173 ms
XNVd6tsqi9wmKNvnh5HNEKCWcynf_cDxXwCLxiixG1c.ttf
181 ms
AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf
179 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
70 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
95 ms
hovercard.css
36 ms
services.css
56 ms
graph.facebook.com
108 ms
g.gif
21 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
19 ms
g.gif
4 ms
syndication
93 ms
423906640543232000
146 ms
proxy.jpg
136 ms
proxy.jpg
308 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
2 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
31BTo87E_normal.png
42 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
29 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
40 ms
proxy.jpg
166 ms
proxy.jpg
221 ms
jot.html
2 ms
eatinscanada.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
button, link, and menuitem elements do not have accessible names.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
eatinscanada.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
eatinscanada.com 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
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 Eatinscanada.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 Eatinscanada.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.
eatinscanada.com
Open Graph data is detected on the main page of Eatinscanada. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: