Tools & Wizards About Us
whynot.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

whynot.com

Discover top-notch deals at the best hotels and restaurants - Whynot.com

Page Load Speed

9.8 sec in total

First Response

188 ms

Resources Loaded

6.1 sec

Page Rendered

3.6 sec

whynot.com screenshot

About Website

Visit whynot.com now to see the best up-to-date Whynot content and also check out these interesting facts you probably never knew about whynot.com

Profit from discounts up to 70% at the finest hotels and restaurants via Whynot.com. ✓ 9+ rating ✓ Discover the best deals

Visit whynot.com

Key Findings

We analyzed Whynot.com page load time and found that the first response time was 188 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

whynot.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value3,330 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

Network Requests Diagram

whynot.com

188 ms

whynot.com

281 ms

3522 ms

whitelabel-icons.css

57 ms

whitelabel.css

58 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 21% of them (17 requests) were addressed to the original Whynot.com, 79% (63 requests) were made to Media.whynot.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Whynot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (18%)

Content Size

10.3 MB

After Optimization

8.4 MB

  • HTML
  • Images
  • CSS

In fact, the total size of Whynot.com main page is 10.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 1.8 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 378.4 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 1.8 MB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 59.8 kB

  • Original 8.1 MB
  • After minification 8.0 MB

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. Whynot images are well optimized though.

CSS Optimization

-85%

Potential reduce by 8.8 kB

  • Original 10.3 kB
  • After minification 8.3 kB
  • After compression 1.5 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. Whynot.com needs all CSS files to be minified and compressed as it can save up to 8.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (7%)

Requests Now

73

After Optimization

68

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whynot.com

whynot.com

188 ms

whynot.com

whynot.com

281 ms

3522 ms

whitelabel-icons.css

whitelabel-icons.css

57 ms

whitelabel.css

whitelabel.css

58 ms

logo.svg

logo.svg

274 ms

offline.svg

offline.svg

1091 ms

iDeal.svg

iDeal.svg

1249 ms

Creditcard.svg

Creditcard.svg

1245 ms

PayPal.svg

PayPal.svg

1864 ms

Visa.svg

Visa.svg

1867 ms

Bancontact.svg

Bancontact.svg

1247 ms

AMEX.svg

AMEX.svg

1250 ms

Sofort.svg

Sofort.svg

1294 ms

en-EN.svg

en-EN.svg

780 ms

discover_hotels.jpg

discover_hotels.jpg

1068 ms

bl_wn_zeeland.jpg

bl_wn_zeeland.jpg

1060 ms

bl_wn_rotterdam.jpg

bl_wn_rotterdam.jpg

1062 ms

bl_wn_scheveningen.jpg

bl_wn_scheveningen.jpg

1060 ms

bl_wn_zandvoort.jpg

bl_wn_zandvoort.jpg

1061 ms

bl_wn_haarlem.jpg

bl_wn_haarlem.jpg

1064 ms

bl_wn_utrecht.jpg

bl_wn_utrecht.jpg

1066 ms

bl_wn_amsterdam.jpg

bl_wn_amsterdam.jpg

1066 ms

bl_wn_valkenburg.jpg

bl_wn_valkenburg.jpg

1068 ms

bl_wn_veluwe.jpg

bl_wn_veluwe.jpg

1069 ms

bl_wn_drenthe.jpg

bl_wn_drenthe.jpg

1070 ms

hotel-prado-21032912072113.jpg

hotel-prado-21032912072113.jpg

1072 ms

hotel-ambassadeur-21092211201513.jpg

hotel-ambassadeur-21092211201513.jpg

1074 ms

vayamundo-oostende-21033111071110.jpg

vayamundo-oostende-21033111071110.jpg

1075 ms

benb-boussemaere-21070613194983.jpg

benb-boussemaere-21070613194983.jpg

1074 ms

tim-torfs-travel-22081617273649.jpg

tim-torfs-travel-22081617273649.jpg

1071 ms

gatsby-boutique-hotel-22033115325091.jpg

gatsby-boutique-hotel-22033115325091.jpg

1074 ms

malecot-hotel-22033015101742.jpg

malecot-hotel-22033015101742.jpg

1100 ms

avenue-boutique-hotel-22033010122228.jpg

avenue-boutique-hotel-22033010122228.jpg

1099 ms

corsendonk-duinse-polders-21101509435619.jpg

corsendonk-duinse-polders-21101509435619.jpg

1098 ms

hotel-le-bois-de-bruges-22022510383379.jpg

hotel-le-bois-de-bruges-22022510383379.jpg

1070 ms

hotel-albert-1-20121715151950.jpg

hotel-albert-1-20121715151950.jpg

1085 ms

vakantielogies-hollywood-22042613560150.jpg

vakantielogies-hollywood-22042613560150.jpg

1083 ms

boutique-hotel-sablon-21090313363961.jpg

boutique-hotel-sablon-21090313363961.jpg

1089 ms

hotel-en-restaurant-central-brugge-21072716241150.jpg

hotel-en-restaurant-central-brugge-21072716241150.jpg

1096 ms

martins-brugge-20121615363564.jpg

martins-brugge-20121615363564.jpg

1090 ms

hotel-ibis-brugge-centrum-21072013152691.jpg

hotel-ibis-brugge-centrum-21072013152691.jpg

1092 ms

novotel-brugge-centrum-21072810394618.jpg

novotel-brugge-centrum-21072810394618.jpg

1095 ms

crowne-plaza-brugge-20081413384415.jpg

crowne-plaza-brugge-20081413384415.jpg

1094 ms

hotel-vredehof-22090915182420.jpg

hotel-vredehof-22090915182420.jpg

1092 ms

le-provencal-21021114214026.jpg

le-provencal-21021114214026.jpg

1097 ms

de-elderschans-22062213201631.jpg

de-elderschans-22062213201631.jpg

1098 ms

hotel-du-commerce-oostburg-21071316025135.jpg

hotel-du-commerce-oostburg-21071316025135.jpg

1100 ms

focus-hotels-22011409343159.jpg

focus-hotels-22011409343159.jpg

1100 ms

ter-heide-22030316084753.jpg

ter-heide-22030316084753.jpg

330 ms

whitelabel-icons.ttf

whitelabel-icons.ttf

331 ms

89ca0be.js

89ca0be.js

237 ms

403a791.js

403a791.js

300 ms

eaf8c62.js

eaf8c62.js

824 ms

22a696a.js

22a696a.js

702 ms

d77a4af.js

d77a4af.js

861 ms

35f010b.js

35f010b.js

807 ms

proxima-soft-medium.woff

proxima-soft-medium.woff

699 ms

proxima-soft-regular.woff

proxima-soft-regular.woff

697 ms

proxima-soft-bold.woff

proxima-soft-bold.woff

633 ms

d-hotel-22072108514415.jpg

d-hotel-22072108514415.jpg

59 ms

stad-en-strandhotel-elisabeth-22040710081034.jpg

stad-en-strandhotel-elisabeth-22040710081034.jpg

58 ms

oostappen-vakantieparken-21031215020346.jpg

oostappen-vakantieparken-21031215020346.jpg

59 ms

hotel-chamade-gent-22042017082098.jpg

hotel-chamade-gent-22042017082098.jpg

155 ms

fletcher.png

fletcher.png

60 ms

novotel.png

novotel.png

58 ms

europarcs.png

europarcs.png

60 ms

centerparcs.png

centerparcs.png

57 ms

corendon.png

corendon.png

60 ms

blacklabelhotels.png

blacklabelhotels.png

58 ms

magnicity.png

magnicity.png

145 ms

holidayinn.png

holidayinn.png

146 ms

bly.png

bly.png

146 ms

vigor.png

vigor.png

144 ms

divin.png

divin.png

125 ms

woods.png

woods.png

125 ms

tantepietje.png

tantepietje.png

124 ms

renaissance.png

renaissance.png

124 ms

cote.png

cote.png

137 ms

zarzo.png

zarzo.png

137 ms

Accessibility Review

whynot.com accessibility score

77

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.

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

High

ARIA IDs are not unique

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

whynot.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

whynot.com SEO score

92

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    X-UA-COMPATIBLE

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whynot.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 Whynot.com main page’s claimed encoding is x-ua-compatible. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

whynot.com

Open Graph data is detected on the main page of Whynot. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: