12.8 sec in total
962 ms
10.7 sec
1.2 sec
Visit sandwichbaron.com now to see the best up-to-date Sandwich Baron content and also check out these interesting facts you probably never knew about sandwichbaron.com
The Sandwich Baron Shops Offer Takeaways and Food Deliveries for Breakfast and Lunch. Free Delivery of Sandwiches, Platters and More.
Visit sandwichbaron.comWe analyzed Sandwichbaron.com page load time and found that the first response time was 962 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
sandwichbaron.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value20.0 s
0/100
25%
Value16.5 s
0/100
10%
Value600 ms
49/100
30%
Value0.039
99/100
15%
Value19.4 s
2/100
10%
962 ms
1276 ms
1960 ms
266 ms
432 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Sandwichbaron.com, 57% (64 requests) were made to Sandwichbaron.co.za and 6% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Sandwichbaron.co.za.
Page size can be reduced by 151.9 kB (11%)
1.4 MB
1.2 MB
In fact, the total size of Sandwichbaron.com main page is 1.4 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 966.8 kB which makes up the majority of the site volume.
Potential reduce by 56.1 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.1 kB or 78% of the original size.
Potential reduce by 29.6 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. Sandwich Baron images are well optimized though.
Potential reduce by 38.5 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 38.5 kB or 17% of the original size.
Potential reduce by 27.7 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. Sandwichbaron.com needs all CSS files to be minified and compressed as it can save up to 27.7 kB or 26% of the original size.
Number of requests can be reduced by 77 (82%)
94
17
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sandwich Baron. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
sandwichbaron.com
962 ms
sandwichbaron.com
1276 ms
www.sandwichbaron.co.za
1960 ms
js
266 ms
js
432 ms
gtm.js
720 ms
dcssb.css
429 ms
colorbox.css
942 ms
style.min.css
1055 ms
style.css
1041 ms
style.css
1043 ms
styles.css
1246 ms
font-awesome.min.css
1236 ms
bootstrap-front.css
1230 ms
css
639 ms
quotes-collection.css
1305 ms
style.css
1314 ms
responsive.css
1331 ms
font-awesome.min.css
1525 ms
elementor-icons.min.css
1533 ms
animations.min.css
1540 ms
frontend-legacy.min.css
1592 ms
frontend.min.css
1611 ms
post-29996.css
1727 ms
all.min.css
1826 ms
v4-shims.min.css
1818 ms
global.css
1810 ms
post-2572.css
1834 ms
css
575 ms
jquery.js
2092 ms
jquery-migrate.min.js
1825 ms
jquery.colorbox-min.js
2012 ms
jquery-colorbox-wrapper-min.js
2027 ms
ga.social_tracking.js
2055 ms
jquery.social.slick.1.0.js
2061 ms
gtm4wp-form-move-tracker.js
2264 ms
quotes-collection.js
2309 ms
responsive-modernizr.min.js
2328 ms
v4-shims.min.js
2507 ms
widgets.js
277 ms
scripts.js
2486 ms
bootstrap.js
2658 ms
accordion.js
2659 ms
responsive-scripts.min.js
2860 ms
jquery.placeholder.min.js
2860 ms
conversion_async.js
439 ms
loader.js
306 ms
js
250 ms
wp-embed.min.js
2379 ms
analytics.js
120 ms
call-tracking_7.js
28 ms
160 ms
collect
42 ms
wcm
64 ms
frontend-modules.min.js
2207 ms
16 ms
position.min.js
1969 ms
dialog.min.js
1968 ms
waypoints.min.js
1985 ms
swiper.min.js
2167 ms
share-link.min.js
1901 ms
frontend.min.js
1955 ms
wp-emoji-release.min.js
1882 ms
gtm.js
362 ms
cropped-logo_web2.png
1031 ms
froweb2.jpg
3210 ms
store-1-1.jpg
1297 ms
store-f-2.jpg
1387 ms
store-f-3.jpg
1157 ms
store-new.jpg
1295 ms
food-d.jpg
1411 ms
facebook.jpg
1595 ms
twitter-icon.png
1614 ms
facebook-icon.png
1614 ms
linkedin-icon.png
1712 ms
googleplus-icon.png
1713 ms
instagram-icon.png
1850 ms
pinterest-icon.png
1855 ms
all.js
239 ms
fbevents.js
234 ms
fontawesome-webfont.woff
2001 ms
fontawesome-webfont.woff
2091 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
295 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff
379 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
598 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff
595 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
598 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff
598 ms
plusone.js
339 ms
167 ms
all.js
66 ms
168 ms
314184349908777
314 ms
widget_iframe.c4bdc17e77719578b594d5555bee90db.html
472 ms
cb=gapi.loaded_0
163 ms
cb=gapi.loaded_1
246 ms
fastbutton
232 ms
252 ms
settings
168 ms
postmessageRelay
417 ms
developers.google.com
1356 ms
button.c6c95b9789db97ea1e9742d215fff751.js
28 ms
embeds
146 ms
tweet_button.c4bdc17e77719578b594d5555bee90db.en.html
122 ms
1832714284-postmessagerelay.js
102 ms
rpc:shindig_random.js
78 ms
cb=gapi.loaded_0
12 ms
fastbutton
128 ms
tab_left_vertical.png
330 ms
bg_slick_top.png
337 ms
95 ms
developers.google.com
397 ms
sandwichbaron.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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
sandwichbaron.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
sandwichbaron.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Sandwichbaron.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 Sandwichbaron.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.
sandwichbaron.com
Open Graph description is not detected on the main page of Sandwich Baron. 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: