1.6 sec in total
154 ms
1.1 sec
341 ms
Welcome to whats.new homepage info - get ready to check Whats best content for India right away, or after learning these important things about whats.new
Discover shortcuts to your favorite actions on the websites you love. Posting, linking, designing, recording — it’s all faster with .new links.
Visit whats.newWe analyzed Whats.new page load time and found that the first response time was 154 ms and then it took 1.5 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.
whats.new performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.2 s
5/100
25%
Value36.3 s
0/100
10%
Value49,950 ms
0/100
30%
Value0.002
100/100
15%
Value86.2 s
0/100
10%
154 ms
144 ms
273 ms
92 ms
70 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 42% of them (21 requests) were addressed to the original Whats.new, 26% (13 requests) were made to Lh3.googleusercontent.com and 20% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (530 ms) relates to the external source Lh3.googleusercontent.com.
Page size can be reduced by 155.3 kB (31%)
500.8 kB
345.5 kB
In fact, the total size of Whats.new main page is 500.8 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. 45% of websites need less resources to load. Images take 217.9 kB which makes up the majority of the site volume.
Potential reduce by 54.2 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 54.2 kB or 83% of the original size.
Potential reduce by 65.9 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 needs image optimization as it can save up to 65.9 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34.2 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 34.2 kB or 16% of the original size.
Potential reduce by 1.1 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. Whats.new needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 14% of the original size.
Number of requests can be reduced by 6 (16%)
38
32
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whats. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for CSS and as a result speed up the page load time.
whats.new
154 ms
whats.new
144 ms
main.min.js
273 ms
gtm.js
92 ms
footer.min.css
70 ms
carousel.min.css
167 ms
cta.min.css
157 ms
modal.min.css
150 ms
main.min.css
133 ms
icon
65 ms
css
83 ms
googlelogo_clr_74x24px.svg
52 ms
C499RlpHUllG3ohcHe5PwhiU_Xp0XjAQZhitwIbQP_ws5HaZ3WMmaSpEOggWR0WTYqyDiDCymnjXNPmWvzqma5U0yhR5-uOR0RWi2hE
107 ms
check_B7C93B37.svg
139 ms
a5osPPaMDev36x_LRweLvYfh2RzOGOMMfXQchr59zcMajQjq3Mohxj9hjZJb6XAXyTLkomWgTyR2P7P6vQN-aNc
228 ms
Jd0Wc1N5Lltnaae5oyx263lHcbho8IGASrE5wnsH-rqwfcqGpPrRnKbN7zSmCgB0bsMxf4MlcaGwbRpAGBzN
317 ms
Y4v39XQkiUoDAO8gA30NU1xDy7dukz03dCTRcUfT89vbHbV7NQV5vzDq4hcT_UoQq9o637GVGFpXfaGt2NTFhA
214 ms
_yAXQdBGupkajYghaobO_FTUdm-z4Fy3tZKn7sCFEVg79TjT2CXDqWf0EOxuGVD9AeGqmr0X8FFUQdC2wu5g
205 ms
y7CbYfsT6HzJFoK8W2VZkbqj9lz-ochRpodEwFZsJ8aBW_MqlfUDSUKdiKGjXTZ2t8TvWKQanCTZbJzgKt3K
211 ms
OVpSdi5eVNeDuJVBOPC7xVPwgERbvxWjgFbj2JRO1GTg7BWzW2BpYg3-sjdFq0Oe177R_dV_eg0DRcs_2zH20w
236 ms
LOGaXbj8L8iMGqGmLpj061cBhNtVm3A7dGwt3bNY4wKvo18B2LikCUbu9zt2f46XIK7XRx4p8WCxunJjvOXXjw
317 ms
z5vj6401gTL1U5SjFlt_4ZeIotSJDiTsrf6OV54junV2bY6b6XtGbYOao7KUMs0YPjbxm-eUuKbr10tBgH3pUw
344 ms
A2DCvnclLVAFU4yGt7STG5HBvDDoODxAKyNjRkP1ATvyb3IYGlCZqe2NpiPSELtaAISXOYJqHQ5VLfmysyInq3A
356 ms
n0XJTscPkUiqIsZ8oagyd4KthMhMXS587KPMEnLAnpJuX9UJ5mpKjkHSSA2fcAerHp-hV8j_YbgsZdXNb55v2g
365 ms
SgehUWclF5R6bY63xcaA4jVl4JZzB7pRXW71WIFIFuVvMLJldEFxnJzyN3rj6zxI80jRjsaLYTbhaKMfiRLhIpo
409 ms
UHwG0LtPxhq6CCDxzY_zk6kLvh2LIaFrETdF6iTFdzpDxGNIrvPAAQyOYAdyU3rkE3jcIyLQRHRIwu5sy8gZ_A
530 ms
logo.svg
293 ms
cards-2.svg
134 ms
cards-3.svg
222 ms
logo.svg
299 ms
logo.svg
263 ms
logo.svg
260 ms
logo.png
293 ms
logo.svg
362 ms
icon-facebook.svg
372 ms
icon-twitter.svg
341 ms
icon-linkedin.svg
390 ms
icon-email.svg
413 ms
icon-link.svg
404 ms
googlelogo_dark54_clr_84x28px.svg
47 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
26 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
41 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzaJ5llpyw.ttf
129 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf
57 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
58 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
58 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
58 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
71 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
59 ms
pxiDypQkot1TnFhsFMOfGShVF9eL.ttf
72 ms
whats.new accessibility score
whats.new best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
whats.new 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 Whats.new 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 Whats.new 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.
whats.new
Open Graph data is detected on the main page of Whats. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: