1.8 sec in total
Visit when.in now to see the best up-to-date When content and also check out these interesting facts you probably never knew about when.in
A new travel app to show where the locals go to eat, drink and play across town or around the world.Visit when.in
We analyzed When.in page load time and found that the first response time was 228 ms and then it took 1.6 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.
when.in performance score
Our browser made a total of 18 requests to load all elements on the main page. We found that 44% of them (8 requests) were addressed to the original When.in, 11% (2 requests) were made to S3.amazonaws.com and 11% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (369 ms) relates to the external source S3.amazonaws.com.
Page size can be reduced by 20.4 kB (3%)
In fact, the total size of When.in main page is 673.2 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. 40% of websites need less resources to load. Images take 503.1 kB which makes up the majority of the site volume.
Potential reduce by 15.7 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 15.7 kB or 76% of the original size.
Potential reduce by 3.0 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. When images are well optimized though.
Potential reduce by 110 B
Potential reduce by 1.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. When.in has all CSS files already compressed.
Number of requests can be reduced by 8 (50%)
when.in accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
<html> element does not have a [lang] attribute
when.in best practices score
Trust and Safety
Does not use HTTPS
Ensure CSP is effective against XSS attacks
when.in SEO score
Document uses legible font sizes
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise When.in 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 When.in 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.
Open Graph data is detected on the main page of When. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: