2.8 sec in total
768 ms
1.7 sec
308 ms
Welcome to cityblue.com homepage info - get ready to check City Blue best content for United States right away, or after learning these important things about cityblue.com
Visit cityblue.comWe analyzed Cityblue.com page load time and found that the first response time was 768 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
cityblue.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value8.1 s
2/100
25%
Value8.3 s
19/100
10%
Value750 ms
39/100
30%
Value0.039
100/100
15%
Value8.1 s
42/100
10%
768 ms
62 ms
69 ms
71 ms
73 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 89% of them (56 requests) were addressed to the original Cityblue.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (768 ms) belongs to the original domain Cityblue.com.
Page size can be reduced by 1.3 MB (47%)
2.9 MB
1.5 MB
In fact, the total size of Cityblue.com main page is 2.9 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. 50% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 43.2 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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.2 kB or 82% of the original size.
Potential reduce by 109.2 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. City Blue images are well optimized though.
Potential reduce by 860.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 860.5 kB or 70% of the original size.
Potential reduce by 330.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. Cityblue.com needs all CSS files to be minified and compressed as it can save up to 330.3 kB or 86% of the original size.
Number of requests can be reduced by 33 (55%)
60
27
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Blue. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
cityblue.com
768 ms
ga.js
62 ms
wp-emoji-release.min.js
69 ms
prettyPhoto.css
71 ms
wp-video-lightbox.css
73 ms
styles.css
72 ms
css
35 ms
style.css
106 ms
jquery.js
122 ms
jquery-migrate.min.js
141 ms
jquery.prettyPhoto.js
144 ms
video-lightbox.js
145 ms
jazzy-forms.js
147 ms
custom.modernizr.js
170 ms
tgf3upk.js
58 ms
public.css
184 ms
flexslider.css
198 ms
public.css
199 ms
animate.css
202 ms
jquery.min.js
7 ms
jquery.bxslider.min.js
228 ms
jquery.form.min.js
267 ms
scripts.js
266 ms
three.min.js
335 ms
sphere.js
267 ms
wp-photo-sphere.js
268 ms
comment-reply.min.js
267 ms
navigation.js
303 ms
wp-embed.min.js
303 ms
jquery.flexslider-min.js
327 ms
jQuery.easing.min.js
329 ms
livechat.js
328 ms
jquery.validate.min.js
369 ms
foundation.min.js
368 ms
jquery.cookie.js
392 ms
script.js
393 ms
user.js
406 ms
__utm.gif
12 ms
cropped-logo1.png
185 ms
bg.png
238 ms
sunflower-1024x6271-1024x347.jpg
325 ms
XR-640.jpg
397 ms
brushes1-1127x382.jpg
357 ms
IMAG0046-1398x475.jpg
390 ms
sketchpadLG-1398x475.jpg
357 ms
services-home.png
437 ms
products-home.png
491 ms
form-home.png
426 ms
NEW-LOGO-ON-BLUE-NO-SQUARE.jpg
435 ms
Protection1-Logo1.jpg
484 ms
marrs.jpg
512 ms
aeg.jpg
522 ms
headshot.jpg
532 ms
af.jpg
534 ms
barf.jpg
578 ms
jeremy.jpg
567 ms
kyle1.jpg
590 ms
grid.png
540 ms
Elusive-Icons.svg
651 ms
skewed-pattern.png
512 ms
1f642.svg
72 ms
is_online
115 ms
bg_direction_nav.png
301 ms
cityblue.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.
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
cityblue.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
cityblue.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cityblue.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 Cityblue.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.
cityblue.com
Open Graph description is not detected on the main page of City Blue. 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: