4.5 sec in total
1.3 sec
2.9 sec
248 ms
Click here to check amazing Why Not content for United States. Otherwise, check out these important facts you probably never knew about whynot.net
Visit whynot.netWe analyzed Whynot.net page load time and found that the first response time was 1.3 sec 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.
whynot.net performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value1.4 s
100/100
25%
Value2.4 s
98/100
10%
Value40 ms
100/100
30%
Value0.278
44/100
15%
Value1.4 s
100/100
10%
1300 ms
243 ms
129 ms
131 ms
125 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that all of those requests were addressed to Whynot.net and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Whynot.net.
Page size can be reduced by 79.2 kB (78%)
101.4 kB
22.2 kB
In fact, the total size of Whynot.net main page is 101.4 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. Only 10% of websites need less resources to load. HTML takes 83.0 kB which makes up the majority of the site volume.
Potential reduce by 75.8 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 10.6 kB, which is 13% 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 75.8 kB or 91% of the original size.
Potential reduce by 3.4 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. Obviously, Why Not needs image optimization as it can save up to 3.4 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
We found no issues to fix!
1
1
The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Not. According to our analytics all requests are already optimized.
whynot.net
1300 ms
main.css
243 ms
front_page.css
129 ms
script.js
131 ms
whynot-logo.png
125 ms
Ayres-Nalebuff_tiny.jpg
625 ms
game-btn.png
639 ms
postproblem-btn.png
123 ms
whynotmerchandise-btn.png
232 ms
book_cover_tile.png
233 ms
bn-bestof.png
627 ms
hearbarryandian-btn.png
1194 ms
otherbooks-btn.png
619 ms
opeds-btn.png
1088 ms
lifecyclebanner.png
961 ms
relatedwebsites-btn.png
756 ms
suggestedreadings-btn.png
954 ms
honesttea-logo.png
971 ms
aboutbook-btn.png
1092 ms
software-btn.png
1213 ms
shutdownBanner.jpg
1100 ms
button_searchnow.png
1095 ms
bulb_brilliant.gif
1216 ms
bulb_ontarget.gif
1224 ms
bulb_soso.gif
1226 ms
bulb_offtarget.gif
1235 ms
bulb_broken.gif
1311 ms
whynot-logo-small.png
1336 ms
whynot.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
whynot.net 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
Browser errors were logged to the console
whynot.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whynot.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Whynot.net 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.
whynot.net
Open Graph description is not detected on the main page of Why Not. 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: