2.1 sec in total
146 ms
1.7 sec
216 ms
Click here to check amazing Dirty Food To content. Otherwise, check out these important facts you probably never knew about dirtyfoodto.com
Dirty Food Eatery is a brunch restaurant located in the Junction neighbourhood of Toronto. We're all about hospitality, comfort food and good ol' fashion home cooking
Visit dirtyfoodto.comWe analyzed Dirtyfoodto.com page load time and found that the first response time was 146 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
dirtyfoodto.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value18.7 s
0/100
25%
Value9.7 s
11/100
10%
Value1,630 ms
12/100
30%
Value0
100/100
15%
Value17.8 s
4/100
10%
146 ms
179 ms
205 ms
39 ms
54 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 28% of them (21 requests) were addressed to the original Dirtyfoodto.com, 53% (40 requests) were made to Cdn2.editmysite.com and 7% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (481 ms) relates to the external source Editmysite.com.
Page size can be reduced by 617.1 kB (16%)
3.8 MB
3.2 MB
In fact, the total size of Dirtyfoodto.com main page is 3.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 44.4 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 44.4 kB or 79% of the original size.
Potential reduce by 481 B
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. Dirty Food To images are well optimized though.
Potential reduce by 571.1 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 571.1 kB or 36% of the original size.
Potential reduce by 1.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. Dirtyfoodto.com has all CSS files already compressed.
Number of requests can be reduced by 30 (56%)
54
24
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dirty Food To. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
dirtyfoodto.com
146 ms
www.dirtyfoodto.com
179 ms
www.dirtyfoodto.com
205 ms
sites.css
39 ms
fancybox.css
54 ms
social-icons.css
51 ms
main_style.css
115 ms
font.css
52 ms
font.css
53 ms
font.css
51 ms
font.css
53 ms
font.css
59 ms
font.css
59 ms
font.css
57 ms
font.css
57 ms
font.css
57 ms
site_membership.css
60 ms
templateArtifacts.js
139 ms
jquery-1.8.3.min.js
58 ms
stl.js
56 ms
main.js
64 ms
main-membership-site.js
62 ms
theme-plugins.js
61 ms
email-decode.min.js
29 ms
ambassador-chat.js
118 ms
plugins.js
319 ms
custom.js
319 ms
main-customer-accounts-site.js
64 ms
form_input_bg.gif
87 ms
widget
354 ms
light-search.png
324 ms
1240259112.jpg
326 ms
07-other-restaurant-shot_orig.jpg
325 ms
breakfast-wich_orig.jpg
324 ms
cookie-smore-2.jpg
325 ms
cookie-strawberry-rhubarb.jpg
333 ms
cookie-cookie-dough.jpg
336 ms
cookie-brownie-explosion.jpg
440 ms
cookie-lemon-coconut.jpg
337 ms
548517388.jpg
337 ms
talk-dirty-to-me-3.jpg
334 ms
regular.ttf
234 ms
regular.woff
237 ms
light.woff
236 ms
bold.woff
236 ms
regular.woff
236 ms
bold.woff
236 ms
italic.woff
242 ms
bolditalic.woff
242 ms
wsocial.svg
238 ms
wsocial.woff
239 ms
wsocial.woff
240 ms
regular.ttf
252 ms
lightitalic.woff
245 ms
italic.woff
241 ms
bolditalic.woff
241 ms
regular.woff
244 ms
bold.woff
244 ms
regular.woff
245 ms
bold.woff
245 ms
generateMap.php
481 ms
waitlist_pages-main-pkg.yji-5febeb665eadbdc4b6fe.css
125 ms
polyfill.min.js
159 ms
module_waitlist_pages_main.yji-bc5bb998618abd057c2a.js
264 ms
ga.js
223 ms
snowday262.js
58 ms
255 ms
242 ms
analytics.js
147 ms
default.yji-4b6a0fc76402800dc81a0a4b080abcb4.png
125 ms
collect
41 ms
collect
44 ms
collect
41 ms
collect
40 ms
js
91 ms
dirtyfoodto.com accessibility score
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
[id] attributes on active, focusable elements 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
dirtyfoodto.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
dirtyfoodto.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 Dirtyfoodto.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 Dirtyfoodto.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.
dirtyfoodto.com
Open Graph data is detected on the main page of Dirty Food To. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: