3.6 sec in total
377 ms
1.7 sec
1.5 sec
Click here to check amazing CBRfoodie content. Otherwise, check out these important facts you probably never knew about cbrfoodie.org
Searching for affordable and tasty food in our nation's capital
Visit cbrfoodie.orgWe analyzed Cbrfoodie.org page load time and found that the first response time was 377 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
cbrfoodie.org performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value6.0 s
13/100
25%
Value7.5 s
26/100
10%
Value2,610 ms
4/100
30%
Value0.007
100/100
15%
Value17.4 s
4/100
10%
377 ms
55 ms
147 ms
173 ms
177 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cbrfoodie.org, 34% (24 requests) were made to Cbrfoodie.files.wordpress.com and 14% (10 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (699 ms) relates to the external source Cbrfoodie.files.wordpress.com.
Page size can be reduced by 434.3 kB (29%)
1.5 MB
1.1 MB
In fact, the total size of Cbrfoodie.org main page is 1.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. 65% of websites need less resources to load. Images take 939.8 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.7 kB or 71% of the original size.
Potential reduce by 2.9 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. CBRfoodie images are well optimized though.
Potential reduce by 358.3 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 358.3 kB or 75% of the original size.
Potential reduce by 31.4 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. Cbrfoodie.org needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 76% of the original size.
Number of requests can be reduced by 28 (47%)
59
31
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CBRfoodie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
cbrfoodie.org
377 ms
webfont.js
55 ms
147 ms
css
173 ms
css
177 ms
139 ms
169 ms
style.css
140 ms
s1.wp.com
138 ms
gprofiles.js
123 ms
wpgroho.js
165 ms
160 ms
jetpack-carousel.css
136 ms
tiled-gallery.css
163 ms
165 ms
widgets.js
162 ms
162 ms
w.js
120 ms
vly2aez.js
312 ms
merriweather.css
27 ms
bg-main.png
145 ms
cropped-cropped-cropped-food_cheapeats3-1_45.jpg
146 ms
a88689e92ab0c57b7a341d057d5cf7fa
144 ms
smile.svg
136 ms
9509a1c0dc6f09e248316b270be4197a
139 ms
widgets.js
130 ms
beanie.jpg
111 ms
smaller-beanie.jpg
324 ms
polo-ordering-window-to-kitchen.jpg
343 ms
polo-wednesday-menu.jpg
329 ms
polo-beer-choice.jpg
328 ms
polo-bar.jpg
330 ms
polo-wheatbeer.jpg
329 ms
polo-dumplings.jpg
354 ms
polo-dumplings-close-up.jpg
464 ms
polo-wall-specials.jpg
465 ms
grant-alicia.png
567 ms
pb0908311.jpg
488 ms
img_7218.jpg
467 ms
img_7168.jpg
535 ms
img_7206.jpg
475 ms
img_7209.jpg
556 ms
img_0932-0.jpg
570 ms
img_1300-1.jpg
573 ms
img_7217.jpg
603 ms
img_7174.jpg
664 ms
img_7157.jpg
699 ms
15ae2e58dff2b70e4be63e6f04acef9c
242 ms
46b3bc818eedff42b4b6cb7af63ad1e5
305 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
411 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
463 ms
bg-main.png
385 ms
cropped-cropped-cropped-food_cheapeats3-1_45.jpg
481 ms
beanie.jpg
485 ms
6dUc_M1PDZZCBfdFvQn4lQ.ttf
380 ms
Noticons.svg
256 ms
BaABdRAi2AAAA
78 ms
merriweather-regular-webfont.ttf
228 ms
merriweather-light-webfont.ttf
228 ms
merriweather-bold-webfont.ttf
254 ms
cbrfoodie.org
450 ms
JAw3QkMFoXWKSJRnfBd9spHMNbFXmDtuxjXtEqac_FJffwWxMUMdeMJ6Mk6f5Mb.woff
34 ms
hovercard.css
71 ms
services.css
72 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
115 ms
g.gif
49 ms
g.gif
27 ms
g.gif
28 ms
p.gif
131 ms
syndication
101 ms
434204349229580288
216 ms
cbrfoodie.org 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
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cbrfoodie.org 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
cbrfoodie.org 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 Cbrfoodie.org 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 Cbrfoodie.org 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.
cbrfoodie.org
Open Graph data is detected on the main page of CBRfoodie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: