1.2 sec in total
95 ms
920 ms
230 ms
Welcome to whatsnext.com homepage info - get ready to check Whats Next best content for United States right away, or after learning these important things about whatsnext.com
Learn how to create a meaningful, satisfying, and fulfilling life you love while building a successful and rewarding career - without wasting precious time, taking wild guesses, or risking it all.
Visit whatsnext.comWe analyzed Whatsnext.com page load time and found that the first response time was 95 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
whatsnext.com performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.8 s
15/100
25%
Value8.2 s
20/100
10%
Value50 ms
100/100
30%
Value0.018
100/100
15%
Value9.9 s
27/100
10%
95 ms
269 ms
146 ms
183 ms
5 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 67% of them (39 requests) were addressed to the original Whatsnext.com, 7% (4 requests) were made to D1n2i0nchws850.cloudfront.net and 5% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (288 ms) belongs to the original domain Whatsnext.com.
Page size can be reduced by 424.0 kB (54%)
790.9 kB
366.9 kB
In fact, the total size of Whatsnext.com main page is 790.9 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. 30% of websites need less resources to load. Javascripts take 550.3 kB which makes up the majority of the site volume.
Potential reduce by 66.3 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 66.3 kB or 74% of the original size.
Potential reduce by 13.6 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, Whats Next needs image optimization as it can save up to 13.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 306.9 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 306.9 kB or 56% of the original size.
Potential reduce by 37.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. Whatsnext.com needs all CSS files to be minified and compressed as it can save up to 37.3 kB or 87% of the original size.
Number of requests can be reduced by 25 (47%)
53
28
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whats Next. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
whatsnext.com
95 ms
www.whatsnext.com
269 ms
f076bd91fdb32c75f9a6cc5affcda64c.css
146 ms
50d5ca953daf2e7f9be3c9c5a718c173.js
183 ms
adsbygoogle.js
5 ms
addthis_widget.js
10 ms
take-the-test-now-.png
113 ms
loader.js
112 ms
loader.js
112 ms
header_bar_top.png
52 ms
logo.png
76 ms
go_button.png
50 ms
main_menu_background.png
110 ms
border_top.gif
78 ms
border.gif
80 ms
border_ulc.gif
102 ms
border_urc.gif
102 ms
border_llc.gif
112 ms
border_lrc.gif
112 ms
picture-795.jpg
149 ms
picture-690.jpg
117 ms
picture-1093.jpg
120 ms
tools_bg.gif
217 ms
blue_bullet.gif
148 ms
more.gif
149 ms
financial_life_bg.gif
152 ms
news_bg.gif
219 ms
round%20linkedin%20logo.jpg
215 ms
follow_facebook%20square.gif
216 ms
follow_twitter%20square.gif
216 ms
border2_top.gif
216 ms
border2.gif
219 ms
border2_ulc.gif
220 ms
border2_urc.gif
238 ms
border2_llc.gif
238 ms
border2_lrc.gif
239 ms
LVAT%20hi%20res%20askew.jpg
271 ms
logo_mbti.gif
252 ms
logo_strong.gif
255 ms
logo_firob.gif
257 ms
cpi260_grey.gif
258 ms
Know%20Yourself%20cover%20small%20with%20Shadow.png
258 ms
careerchange.gif
288 ms
find-out-more.png
39 ms
ga.js
34 ms
take-the-free-test-now-.png
8 ms
find-out-more.png
9 ms
salog.js.aspx
80 ms
__utm.gif
14 ms
85859.js
153 ms
300lo.json
49 ms
340.89e90439938e0cc58210.js
9 ms
loader.gif
84 ms
sh.7c7179124ea24ac6ba46caac.html
24 ms
2230
36 ms
pixel
23 ms
pixel
24 ms
match-result
5 ms
whatsnext.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
Form elements do not have associated labels
Links do not have a discernible 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
whatsnext.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
whatsnext.com SEO score
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 Whatsnext.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 Whatsnext.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.
whatsnext.com
Open Graph description is not detected on the main page of Whats Next. 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: