1.3 sec in total
26 ms
1.1 sec
238 ms
Visit dining.ca now to see the best up-to-date Dining content and also check out these interesting facts you probably never knew about dining.ca
N49 Helps you find the best businesses in Canadian communities
Visit dining.caWe analyzed Dining.ca page load time and found that the first response time was 26 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
dining.ca performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value3.2 s
72/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0.273
45/100
15%
Value3.1 s
95/100
10%
26 ms
134 ms
137 ms
288 ms
283 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dining.ca, 41% (26 requests) were made to Static.n49.ca and 22% (14 requests) were made to N49.com. The less responsive or slowest element that took the longest time to load (337 ms) relates to the external source Static.n49.ca.
Page size can be reduced by 881.1 kB (71%)
1.2 MB
353.4 kB
In fact, the total size of Dining.ca main page is 1.2 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. Javascripts take 816.0 kB which makes up the majority of the site volume.
Potential reduce by 48.3 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. This page needs HTML code to be minified as it can gain 9.6 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.3 kB or 76% of the original size.
Potential reduce by 52.4 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, Dining needs image optimization as it can save up to 52.4 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 596.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 596.0 kB or 73% of the original size.
Potential reduce by 184.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. Dining.ca needs all CSS files to be minified and compressed as it can save up to 184.3 kB or 85% of the original size.
Number of requests can be reduced by 35 (64%)
55
20
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dining. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
dining.ca
26 ms
www.n49.com
134 ms
css
137 ms
general-styles.css
288 ms
review-iframe.css
283 ms
video-js.min.css
281 ms
jquery.min.js
139 ms
javascriptconf.php
110 ms
LAB.min.js
275 ms
centralizedlogin.js
277 ms
jquery.carouFredSel-5.2.3-packed.js
285 ms
n49.js
320 ms
stats_tracker.js
316 ms
reviews.js
319 ms
review-assets.js
317 ms
video.js
328 ms
videos.js
318 ms
bootstrap.css
327 ms
main.css
335 ms
signInAs.js
333 ms
nl-icons.css
333 ms
nl-admin.css
334 ms
plugins.js
337 ms
typeahead.bundle.min.js
123 ms
hogan.common.js
237 ms
algoliasearch.min.js
314 ms
search.js
333 ms
white.gif
8 ms
us-flag.jpg
6 ms
uk-flag.jpg
8 ms
logo_medium.gif
7 ms
gtm.js
125 ms
1
48 ms
print.css
16 ms
homepage-banner.jpg
19 ms
css
61 ms
bootstrap.min.css
61 ms
nouislider.min.css
78 ms
introjs.min.css
78 ms
main.css
93 ms
js
159 ms
bundle.js
196 ms
getsession.php
158 ms
query
236 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
101 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
114 ms
mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf
116 ms
analytics.js
85 ms
prum.min.js
171 ms
collect
5 ms
collect
91 ms
inform_login.php
77 ms
logo.png
30 ms
query
123 ms
search-suggestion.hbs
66 ms
1
44 ms
logo.svg
19 ms
mobile-login-image.png
16 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
6 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
6 ms
n49search.woff
42 ms
nr-885.min.js
47 ms
collect
11 ms
dining.ca accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dining.ca best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
dining.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dining.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 Dining.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.
dining.ca
Open Graph description is not detected on the main page of Dining. 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: