2 sec in total
291 ms
1.4 sec
259 ms
Visit citysaver.com now to see the best up-to-date City Saver content for United States and also check out these interesting facts you probably never knew about citysaver.com
Our Coupons Are Mobile…Just Like You! Over $10,000 in discounts on the City Saver mobile app! Save in Nashville, Memphis, Cincinnati & more!
Visit citysaver.comWe analyzed Citysaver.com page load time and found that the first response time was 291 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
citysaver.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value7.9 s
3/100
25%
Value5.4 s
56/100
10%
Value740 ms
40/100
30%
Value0
100/100
15%
Value8.5 s
38/100
10%
291 ms
39 ms
40 ms
139 ms
405 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 71% of them (49 requests) were addressed to the original Citysaver.com, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Dsms0mj1bbhn4.cloudfront.net. The less responsive or slowest element that took the longest time to load (509 ms) belongs to the original domain Citysaver.com.
Page size can be reduced by 1.4 MB (64%)
2.2 MB
807.2 kB
In fact, the total size of Citysaver.com main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 213.9 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 213.9 kB or 90% of the original size.
Potential reduce by 25.3 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 Saver images are well optimized though.
Potential reduce by 756.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 756.5 kB or 70% of the original size.
Potential reduce by 423.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. Citysaver.com needs all CSS files to be minified and compressed as it can save up to 423.4 kB or 86% of the original size.
Number of requests can be reduced by 35 (53%)
66
31
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Saver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
citysaver.com
291 ms
ga.js
39 ms
shareaholic.js
40 ms
wp-emoji-release.min.js
139 ms
formidablepro.css
405 ms
q-a-plus.css
147 ms
tubepress.css
148 ms
jquery.bxslider.css
147 ms
testimonials-widget.css
146 ms
social_widget.css
206 ms
royalslider.css
219 ms
rs-citysaver.css
210 ms
style.css
276 ms
advanced-recent-posts-widget.css
201 ms
jquery.js
397 ms
jquery-migrate.min.js
273 ms
tubepress.js
273 ms
modernizr.custom.min.js
274 ms
q-a-plus.js
339 ms
scripts.js
341 ms
wp-embed.min.js
344 ms
jquery.royalslider.min.js
452 ms
__utm.gif
15 ms
fb8effd2ef82eb5f339111d667dbbacf.json
48 ms
bkgd_city.jpg
224 ms
bg-inner-header.png
223 ms
header_citysaver.png
226 ms
btn_search_dark.png
223 ms
choose_city_button.png
223 ms
2016-books-Slider-New.jpg
225 ms
raisemoney_slide1.jpg
225 ms
blank.gif
224 ms
savemoney_slide.jpg
305 ms
advertise_slide.jpg
225 ms
form_bkgd2.png
304 ms
citysaver_icons.jpg
304 ms
buy-the-book-button.png
302 ms
activate_the_app_button.png
302 ms
raise_money_button.png
302 ms
facebook.png
474 ms
twitter.png
473 ms
linkedin.png
470 ms
youtube.png
472 ms
foursquare.png
470 ms
googleplus.png
468 ms
pinterest.png
508 ms
advertise_sidebar.png
509 ms
email.png
508 ms
bkgd_footer.jpg
497 ms
footer_lightbulb.png
497 ms
shrMain.min.js
124 ms
0r0xuzzT16s
213 ms
bg-primary-submenu.png
299 ms
preloader.gif
429 ms
rs-default-inverted.png
404 ms
3gMdxRbSZFE
159 ms
jquery.min.js
92 ms
analytics.js
22 ms
www-embed-player-vflfNyN_r.css
145 ms
www-embed-player.js
174 ms
pageview.gif
45 ms
vglnk.js
83 ms
partners.js
172 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
72 ms
ad_status.js
129 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
88 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
85 ms
pixel.gif
13 ms
pixel.gif
63 ms
citysaver.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
citysaver.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
citysaver.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 Citysaver.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 Citysaver.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.
citysaver.com
Open Graph description is not detected on the main page of City Saver. 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: