Tools & Wizards About Us
when.in screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

when.in

when.in. go where the locals go™

Page Load Speed

1.8 sec in total

First Response

228 ms

Resources Loaded

1.4 sec

Page Rendered

242 ms

when.in screenshot

About Website

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

Key Findings

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 35% of websites can load faster.

Performance Metrics

when.in performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

when.in

228 ms

vendor-styles.css

15 ms

styles.css

10 ms

site.css

168 ms

jquery.min.js

68 ms

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 Optimization Overview & Recommendations

Page size can be reduced by 20.4 kB (3%)

Content Size

673.2 kB

After Optimization

652.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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.

HTML Optimization

-76%

Potential reduce by 15.7 kB

  • Original 20.5 kB
  • After minification 19.8 kB
  • After compression 4.9 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.

Image Optimization

-1%

Potential reduce by 3.0 kB

  • Original 503.1 kB
  • After minification 500.1 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.

JavaScript Optimization

-0%

Potential reduce by 110 B

  • Original 127.0 kB
  • After minification 127.0 kB
  • After compression 126.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 1.6 kB

  • Original 22.6 kB
  • After minification 22.6 kB
  • After compression 21.0 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.

Requests Breakdown

Number of requests can be reduced by 8 (50%)

Requests Now

16

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of When. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

when.in

when.in

228 ms

vendor-styles.css

vendor-styles.css

15 ms

styles.css

styles.css

10 ms

site.css

site.css

168 ms

jquery.min.js

jquery.min.js

68 ms

vendor-scripts.min.js

vendor-scripts.min.js

67 ms

scripts.min.js

scripts.min.js

9 ms

lr-site.js

lr-site.js

10 ms

css

css

27 ms

0vo3eq-wi%20app%20old.png

0vo3eq-wi%20app%20old.png

369 ms

loading.gif

loading.gif

258 ms

analytics.js

analytics.js

128 ms

piwik.js

piwik.js

219 ms

sugz9k-hk%20wi.jpeg

sugz9k-hk%20wi.jpeg

182 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

49 ms

collect

collect

6 ms

collect

collect

91 ms

ga-audiences

ga-audiences

56 ms

Accessibility Review

when.in accessibility score

97

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

when.in best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

when.in SEO score

100

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

    N/A

  • Encoding

    UTF-8

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.

Social Sharing Optimization

when.in

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: