5.7 sec in total
989 ms
4.3 sec
394 ms
Visit eatdrinkboulder.com now to see the best up-to-date Eat Drink Boulder content for United States and also check out these interesting facts you probably never knew about eatdrinkboulder.com
News, Views, and Happenings in Boulder's Food and Drink Scene
Visit eatdrinkboulder.comWe analyzed Eatdrinkboulder.com page load time and found that the first response time was 989 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eatdrinkboulder.com performance score
name
value
score
weighting
Value3.1 s
45/100
10%
Value6.7 s
7/100
25%
Value3.7 s
86/100
10%
Value950 ms
29/100
30%
Value0.189
65/100
15%
Value6.9 s
54/100
10%
989 ms
52 ms
84 ms
91 ms
87 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 51% of them (61 requests) were addressed to the original Eatdrinkboulder.com, 17% (20 requests) were made to Dotcal-com-syndical.netdna-ssl.com and 8% (10 requests) were made to Dotcal.com. The less responsive or slowest element that took the longest time to load (989 ms) belongs to the original domain Eatdrinkboulder.com.
Page size can be reduced by 471.6 kB (33%)
1.4 MB
952.6 kB
In fact, the total size of Eatdrinkboulder.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. 65% of websites need less resources to load. Images take 868.1 kB which makes up the majority of the site volume.
Potential reduce by 34.0 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 34.0 kB or 78% of the original size.
Potential reduce by 59.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. Eat Drink Boulder images are well optimized though.
Potential reduce by 241.9 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 241.9 kB or 70% of the original size.
Potential reduce by 135.8 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. Eatdrinkboulder.com needs all CSS files to be minified and compressed as it can save up to 135.8 kB or 82% of the original size.
Number of requests can be reduced by 79 (71%)
112
33
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eat Drink Boulder. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
eatdrinkboulder.com
989 ms
style.css
52 ms
main.css
84 ms
style.css
91 ms
modal.css
87 ms
jquery-ui.css
46 ms
social_widget.css
91 ms
widget.css
101 ms
shortcode.css
106 ms
prettyPhoto.css
106 ms
swfobject.js
110 ms
global.js
114 ms
tiles.js
138 ms
modal.js
138 ms
twitterUsers.js
139 ms
twitterConversations.js
139 ms
bounce.js
144 ms
fma.js
179 ms
jquery.js
238 ms
jquery-migrate.min.js
444 ms
jquery.ui.core.min.js
177 ms
jquery.ui.widget.min.js
170 ms
jquery.ui.position.min.js
209 ms
jquery.ui.menu.min.js
207 ms
jquery.ui.autocomplete.min.js
208 ms
autocomplete.js
234 ms
slides.min.jquery.js
255 ms
feedback.js
250 ms
jquery.prettyPhoto.js
251 ms
general.js
252 ms
css
85 ms
shortcodes.css
252 ms
custom.css
258 ms
trigger_buttons.min.css
262 ms
shutter.min.css
262 ms
font-awesome.min.css
267 ms
style.min.css
273 ms
nggallery.css
280 ms
style.css
303 ms
comment-reply.min.js
241 ms
ajax.min.js
246 ms
common.min.js
258 ms
lightbox_context.min.js
261 ms
shutter.min.js
349 ms
nextgen_shutter.min.js
342 ms
textured-background.jpg
473 ms
embed
442 ms
edb-logos-073.jpg
302 ms
alert-overlay.png
143 ms
ico-social-rss.png
145 ms
ico-social-twitter.png
147 ms
ico-social-facebook.png
147 ms
20160209_100124_resize-610x300.jpg
444 ms
Spicy-Veg-with-tea.jpeg
441 ms
IMAG0562-610x300.jpg
720 ms
EClark_150328_1273-610x300.jpg
440 ms
wine.jpg
440 ms
btn-prev-slider.png
442 ms
btn-next-slider.png
443 ms
widgets.js
280 ms
ico-search.png
398 ms
xgzbb53t8j-Mo-vYa23n5nhCUOGz7vYGh680lGh-uXM.woff
346 ms
C6HYlRF50SGJq1XyXj04z3l4twXkwp3_u9ZoePkT564.woff
387 ms
ga.js
342 ms
arrow-superfish.png
305 ms
03aPdn7fFF3H6ngCgAlQzBsxEYwM7FgeyaSgU71cLG0.woff
424 ms
Foydq9xJp--nfYIx2TBz9QFhaRv2pGgT5Kf0An0s4MM.woff
417 ms
sDRi4fY9bOiJUbgq53yZCfesZW2xOQ-xsNqO47m55DA.woff
456 ms
QABk9IxT-LFTJ_dQzv7xpIbN6UDyHWBl620a-IRfuBk.woff
277 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
322 ms
jquery.min.js
198 ms
jquery-migrate-1.2.1.min.js
223 ms
jquery-ui.min.js
244 ms
1459973768-embed-download-min.js
785 ms
imgLiquid.js
363 ms
1459973768-embed-base-min.css
542 ms
notrounded.css
504 ms
jquery-ui-.custom.css
544 ms
__utm.gif
163 ms
syndication
200 ms
347595530706235392
435 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
61 ms
ui.base.css
240 ms
ajax-loader.gif
162 ms
syndical-logo18hx78w.png
226 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
19 ms
EDB_logo_for_Twitter_normal.jpg
380 ms
0SNjcsQm_normal.jpg
425 ms
UwDOmLEu_normal.jpg
470 ms
3s1y3hDc_normal.jpeg
730 ms
CfZ_U3XUAAAK46b.jpg:small
732 ms
CfIuMD8VAAASGHT.jpg:small
706 ms
Ce0NGy9VIAEkkDl.jpg:small
729 ms
ui.core.css
188 ms
ui.resizable.css
189 ms
ui.accordion.css
191 ms
ui.dialog.css
191 ms
ui.slider.css
188 ms
ui.tabs.css
292 ms
ui.datepicker.css
319 ms
ui.progressbar.css
321 ms
jot
63 ms
ui-bg_flat_75_ffffff_40x100.png
234 ms
ui-bg_flat_75_f9f5ea_40x100.png
233 ms
ui-icons_000000_256x240.png
232 ms
syndicalbutton18hx18w.png
128 ms
googlebutton.png
77 ms
yahoobutton.png
75 ms
phonebutton.png
86 ms
icalbutton.png
86 ms
outlookbutton.png
113 ms
thunderbirdbutton.png
112 ms
ui-bg_flat_65_ffffff_40x100.png
185 ms
outlook2003button.png
185 ms
outlook2007button.png
186 ms
__utm.gif
22 ms
collect
663 ms
20160209_100124_resize-610x300.jpg
148 ms
loading.png
118 ms
slider-pagination.png
68 ms
eatdrinkboulder.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 IDs 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
Links do not have a discernible name
eatdrinkboulder.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eatdrinkboulder.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 Eatdrinkboulder.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 Eatdrinkboulder.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.
eatdrinkboulder.com
Open Graph description is not detected on the main page of Eat Drink Boulder. 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: