Tools & Wizards About Us
yaysavings.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

yaysavings.com

Top Retail Coupons, Promo Codes and Sales | Yay Savings

Page Load Speed

1.3 sec in total

First Response

214 ms

Resources Loaded

877 ms

Page Rendered

229 ms

yaysavings.com screenshot

About Website

Visit yaysavings.com now to see the best up-to-date Yay Savings content for United States and also check out these interesting facts you probably never knew about yaysavings.com

Looking for free coupons, coupon codes, sales, grocery coupons and flash sales? Yaysavings.com has them all.

Visit yaysavings.com

Key Findings

We analyzed Yaysavings.com page load time and found that the first response time was 214 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

yaysavings.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.084

93/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

yaysavings.com

214 ms

fonts.css

71 ms

font-awesome.min.css

109 ms

desktop.css

124 ms

jquery-1.11.2.min.js

162 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 87% of them (46 requests) were addressed to the original Yaysavings.com, 4% (2 requests) were made to Connect.facebook.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (281 ms) belongs to the original domain Yaysavings.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.8 kB (54%)

Content Size

655.1 kB

After Optimization

300.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yaysavings.com main page is 655.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 255.2 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 40.8 kB

  • Original 48.7 kB
  • After minification 39.7 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 19% 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 40.8 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 9.7 kB

  • Original 143.9 kB
  • After minification 134.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. Yay Savings images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 123.7 kB

  • Original 255.2 kB
  • After minification 230.6 kB
  • After compression 131.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 123.7 kB or 48% of the original size.

CSS Optimization

-87%

Potential reduce by 180.6 kB

  • Original 207.3 kB
  • After minification 152.1 kB
  • After compression 26.6 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. Yaysavings.com needs all CSS files to be minified and compressed as it can save up to 180.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (31%)

Requests Now

45

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yay Savings. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yaysavings.com

yaysavings.com

214 ms

fonts.css

fonts.css

71 ms

font-awesome.min.css

font-awesome.min.css

109 ms

desktop.css

desktop.css

124 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

162 ms

yayfuncs.js

yayfuncs.js

76 ms

main.js

main.js

91 ms

iscroll.js

iscroll.js

156 ms

slidermenu.js

slidermenu.js

102 ms

yaysearch.js

yaysearch.js

121 ms

sdk.js

sdk.js

18 ms

yaysocial.js

yaysocial.js

114 ms

adsbygoogle.js

adsbygoogle.js

65 ms

analytics.js

analytics.js

200 ms

yaylogo.png

yaylogo.png

83 ms

deals-bg.jpg

deals-bg.jpg

86 ms

flame-left.png

flame-left.png

83 ms

flame-right.png

flame-right.png

83 ms

800009.gif

800009.gif

81 ms

39791.gif

39791.gif

83 ms

800069.gif

800069.gif

86 ms

800066.gif

800066.gif

131 ms

800072.gif

800072.gif

83 ms

10685.gif

10685.gif

132 ms

31236.gif

31236.gif

131 ms

800142.gif

800142.gif

130 ms

800039.gif

800039.gif

128 ms

5482.gif

5482.gif

140 ms

26841.gif

26841.gif

181 ms

82.gif

82.gif

147 ms

31223.gif

31223.gif

153 ms

18814.gif

18814.gif

146 ms

25831.gif

25831.gif

169 ms

800090.gif

800090.gif

195 ms

4004.gif

4004.gif

199 ms

800077.gif

800077.gif

249 ms

800128.gif

800128.gif

254 ms

800001.gif

800001.gif

281 ms

800015.gif

800015.gif

239 ms

store-logo-banner.png

store-logo-banner.png

267 ms

sdk.js

sdk.js

74 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

189 ms

OpenSans-CondensedBold-webfont.woff

OpenSans-CondensedBold-webfont.woff

210 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

229 ms

OpenSans-CondensedLight-webfont.woff

OpenSans-CondensedLight-webfont.woff

200 ms

OpenSans-Bold-webfont.woff

OpenSans-Bold-webfont.woff

211 ms

OpenSans-webfont.woff

OpenSans-webfont.woff

221 ms

Socialico-webfont.woff

Socialico-webfont.woff

229 ms

collect

collect

55 ms

collect

collect

63 ms

yay120x60.png

yay120x60.png

186 ms

js

js

52 ms

mobile.css

mobile.css

39 ms

Accessibility Review

yaysavings.com accessibility score

73

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yaysavings.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yaysavings.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yaysavings.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 Yaysavings.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.

Social Sharing Optimization

yaysavings.com

Open Graph description is not detected on the main page of Yay Savings. 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: