1.8 sec in total
26 ms
1.1 sec
667 ms
Visit 2msmokehouse.com now to see the best up-to-date 2M Smokehouse content and also check out these interesting facts you probably never knew about 2msmokehouse.com
Visit 2msmokehouse.comWe analyzed 2msmokehouse.com page load time and found that the first response time was 26 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
2msmokehouse.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value11.2 s
0/100
25%
Value6.7 s
36/100
10%
Value680 ms
44/100
30%
Value0.194
63/100
15%
Value9.8 s
28/100
10%
26 ms
86 ms
86 ms
51 ms
158 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original 2msmokehouse.com, 59% (49 requests) were made to Static.spotapps.co and 5% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (754 ms) relates to the external source Res.cloudinary.com.
Page size can be reduced by 177.0 kB (7%)
2.5 MB
2.3 MB
In fact, the total size of 2msmokehouse.com main page is 2.5 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. 75% 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.2 MB which makes up the majority of the site volume.
Potential reduce by 115.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 115.7 kB or 82% of the original size.
Potential reduce by 47.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. 2M Smokehouse images are well optimized though.
Potential reduce by 7.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 6.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. 2msmokehouse.com has all CSS files already compressed.
Number of requests can be reduced by 37 (51%)
73
36
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2M Smokehouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
2msmokehouse.com
26 ms
2msmokehouse.com
86 ms
js
86 ms
bootstrap.min.css
51 ms
gallery.css
158 ms
jquery.fancybox.css
114 ms
jquery.fancybox-thumbs.css
158 ms
uikit.docs.min.css
57 ms
slidenav.css
69 ms
font-awesome.min.css
64 ms
hover-min.css
65 ms
owl.carousel.min.css
69 ms
owl.theme.default.min.css
69 ms
leaflet.css
77 ms
style.css
71 ms
bottom_navigation_v1.css
112 ms
custom.css
30 ms
social_icons.css
77 ms
lazysizes.min.js
77 ms
jquery.min.js
77 ms
jquery.browser.min.js
208 ms
bootstrap.min.js
108 ms
owl.carousel.min.js
153 ms
masonry.pkgd.min.js
110 ms
uikit.min.js
111 ms
slideshow.min.js
111 ms
imagesloaded.pkgd.min.js
277 ms
jquery.fancybox.js
266 ms
jquery.fancybox.pack.js
287 ms
jquery.fancybox-thumbs.js
287 ms
jquery.fancybox-media.js
277 ms
iframeResizer.js
268 ms
leaflet.js
110 ms
leaflet-providers.js
266 ms
cover_video_play_stop_button_mt_v6+2.js
267 ms
css2
79 ms
css
42 ms
js
301 ms
analytics.js
356 ms
:original
543 ms
:original
721 ms
:original
668 ms
:original
754 ms
logo.png
311 ms
logo_onscroll.png
371 ms
video_cover.jpg
350 ms
our_story_bg.jpg
304 ms
ourstory_left.jpg
368 ms
parties_catering_bg.jpg
304 ms
parties_right.jpg
452 ms
parties_catering_title_decor.png
370 ms
catering_left.jpg
482 ms
order_online_bg.jpg
405 ms
gallery_back_2.png
455 ms
placeholder.png
404 ms
reviews_bg.jpg
438 ms
newsletter_bg.jpg
525 ms
spothopper-logo-new.png
482 ms
MwQ5bhbm2POE6Vg.ttf
313 ms
fontawesome-webfont.woff
460 ms
fontawesome-webfont.woff
486 ms
fontawesome-webfont.woff
414 ms
pxiHypAnsdxUm159X7D-.ttf
371 ms
XLYgIZbkc4JPUL5CVArUVL0nhnc.ttf
434 ms
XLYgIZbkc4JPUL5CVArUVL0ntnAOTQ.ttf
390 ms
marker-icon.png
135 ms
27167.png
217 ms
27167.png
217 ms
27166.png
232 ms
27168.png
258 ms
marker-shadow.png
173 ms
27168.png
222 ms
27166.png
221 ms
27167.png
223 ms
27168.png
222 ms
27167.png
223 ms
27166.png
220 ms
27166.png
206 ms
27168.png
219 ms
fontawesome-webfont.ttf
64 ms
newsletter.js
28 ms
newsletter.js
29 ms
loading.gif
4 ms
2msmokehouse.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
[aria-hidden="true"] elements contain focusable descendents
2msmokehouse.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
Browser errors were logged to the console
2msmokehouse.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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 2msmokehouse.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 2msmokehouse.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.
2msmokehouse.com
Open Graph description is not detected on the main page of 2M Smokehouse. 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: