Tools & Wizards About Us
whatsay.com screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

1.2 sec in total

First Response

43 ms

Resources Loaded

1 sec

Page Rendered

138 ms

whatsay.com screenshot

About Website

Welcome to whatsay.com homepage info - get ready to check What Say best content for India right away, or after learning these important things about whatsay.com

Visit whatsay.com

Key Findings

We analyzed Whatsay.com page load time and found that the first response time was 43 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.

Performance Metrics

whatsay.com performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.7 s

99/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

00AjC

43 ms

whatsay.com

614 ms

counter.js

17 ms

t.php

149 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whatsay.com, 25% (1 request) were made to Ketmo.com and 25% (1 request) were made to Statcounter.com. The less responsive or slowest element that took the longest time to load (614 ms) relates to the external source Ketmo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.1 kB (40%)

Content Size

30.2 kB

After Optimization

18.1 kB

  • HTML
  • JavaScript

In fact, the total size of Whatsay.com main page is 30.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. Only 5% of websites need less resources to load. HTML takes 15.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 10.6 kB

  • Original 15.1 kB
  • After minification 14.7 kB
  • After compression 4.5 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 10.6 kB or 70% of the original size.

JavaScript Optimization

-10%

Potential reduce by 1.5 kB

  • Original 15.1 kB
  • After minification 15.1 kB
  • After compression 13.6 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.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • Images
  • JavaScript

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What Say. According to our analytics all requests are already optimized.

Network Requests Diagram

00AjC

00AjC

43 ms

whatsay.com

whatsay.com

614 ms

counter.js

counter.js

17 ms

t.php

t.php

149 ms

Accessibility Review

whatsay.com accessibility score

94

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

whatsay.com best practices score

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

whatsay.com SEO score

67

Search Engine Optimization Advices

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 Whatsay.com 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 Whatsay.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.

Social Sharing Optimization

whatsay.com

Open Graph description is not detected on the main page of What Say. 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: