2.5 sec in total
39 ms
1.8 sec
668 ms
Click here to check amazing One Twenty Three Burger House content. Otherwise, check out these important facts you probably never knew about onetwentythreeburgerhouse.com
Visit onetwentythreeburgerhouse.comWe analyzed Onetwentythreeburgerhouse.com page load time and found that the first response time was 39 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
onetwentythreeburgerhouse.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value5.4 s
21/100
25%
Value10.1 s
9/100
10%
Value3,620 ms
1/100
30%
Value0.041
99/100
15%
Value20.8 s
2/100
10%
39 ms
54 ms
25 ms
34 ms
47 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 61% of them (60 requests) were addressed to the original Onetwentythreeburgerhouse.com, 24% (24 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (738 ms) relates to the external source Fonts.gstatic.com.
Page size can be reduced by 134.5 kB (4%)
3.2 MB
3.1 MB
In fact, the total size of Onetwentythreeburgerhouse.com main page is 3.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. 85% 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.5 MB which makes up the majority of the site volume.
Potential reduce by 59.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. 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 59.3 kB or 80% of the original size.
Potential reduce by 16.8 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. One Twenty Three Burger House images are well optimized though.
Potential reduce by 30.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. This website has mostly compressed JavaScripts.
Potential reduce by 28.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. Onetwentythreeburgerhouse.com needs all CSS files to be minified and compressed as it can save up to 28.3 kB or 13% of the original size.
Number of requests can be reduced by 43 (61%)
71
28
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of One Twenty Three Burger House. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
onetwentythreeburgerhouse.com
39 ms
www.onetwentythreeburgerhouse.com
54 ms
style.min.css
25 ms
styles.css
34 ms
js_composer.min.css
47 ms
bootstrap.min.css
37 ms
core.min.css
28 ms
theme.min.css
65 ms
font-awesome.min.css
45 ms
magnific-popup.css
63 ms
themesion-base-icons.css
69 ms
balloon.min.css
76 ms
admin-ajax.php
398 ms
responsive.min.css
69 ms
css
66 ms
css
61 ms
lightbox.min.css
68 ms
owl.min.css
70 ms
animate.min.css
69 ms
jquery.min.js
72 ms
jquery-migrate.min.js
73 ms
addon-scripts.js
71 ms
jquery.magnific-popup.min.js
73 ms
jquery.sticky-kit.min.js
75 ms
core.min.js
74 ms
js
73 ms
css
63 ms
css
61 ms
rs6.css
79 ms
index.js
95 ms
index.js
75 ms
rbtools.min.js
80 ms
rs6.min.js
83 ms
isotope.pkgd.min.js
84 ms
js_composer_front.min.js
90 ms
lightbox.min.js
93 ms
owl.carousel.min.js
92 ms
imagesloaded.pkgd.min.js
91 ms
underscore.min.js
100 ms
vc-waypoints.min.js
101 ms
vc_grid.min.js
105 ms
wood-background.jpg
51 ms
123burgerlogo.png
53 ms
dummy.png
49 ms
hours.png
53 ms
location-161x48.png
51 ms
building2-400x150.jpg
51 ms
fire.png
52 ms
talk-to-us.png
53 ms
XsYxbRRF5-g
306 ms
hrQQIG4LPSE
644 ms
pizza-fire.png
153 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLQyN_S5As.ttf
261 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLcSN_S5As.ttf
275 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLHSN_S5As.ttf
302 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLwyN_S5As.ttf
300 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLQyJ_S5As.ttf
738 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLnSR_S5As.ttf
288 ms
V8mqoQfxVT4Dvddr_yOwrzaFxV7JtdQgFqXdUAQrGp_zgX5sWCpLpCR_S5As.ttf
288 ms
pONk1hggFNmwvXALyH6irIP8.ttf
313 ms
themesion-base-icons.woff
91 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr.ttf
146 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
190 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
190 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
191 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lCds18E.ttf
191 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSds18E.ttf
216 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklyds18E.ttf
217 ms
6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDc.ttf
217 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkids18E.ttf
217 ms
6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokSds18E.ttf
218 ms
J7aRnpd8CGxBHpUutLY.ttf
220 ms
J7acnpd8CGxBHp2VkaY_zps.ttf
219 ms
www-player.css
72 ms
www-embed-player.js
116 ms
base.js
147 ms
prev.png
43 ms
admin-ajax.php
590 ms
next.png
39 ms
loading.gif
39 ms
close.png
38 ms
ad_status.js
338 ms
QGccEJWqd_gIzr4UnyRjJu4DFpzUq3q8RcWI0eePlNs.js
246 ms
embed.js
152 ms
123burger-8-600x480.jpg
24 ms
123burger-6-600x480.jpg
78 ms
123burger-5-600x480.jpg
20 ms
123burger-1-600x480.jpg
71 ms
123burger-4-600x480.jpg
22 ms
123-burgers-600x480.jpg
21 ms
123-burgers-6-600x480.jpg
77 ms
123-burgers-3-600x480.jpg
76 ms
123-burgers-1-600x480.jpg
76 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
16 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
15 ms
id
61 ms
onetwentythreeburgerhouse.com accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
onetwentythreeburgerhouse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
onetwentythreeburgerhouse.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onetwentythreeburgerhouse.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 Onetwentythreeburgerhouse.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.
onetwentythreeburgerhouse.com
Open Graph description is not detected on the main page of One Twenty Three Burger House. 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: