Report Summary

  • 79

    Performance

    Renders faster than
    86% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

694 ms in total

First Response

214 ms

Resources Loaded

326 ms

Page Rendered

154 ms

About Website

Visit whobis.com now to see the best up-to-date Whobis content for India and also check out these interesting facts you probably never knew about whobis.com

Whois Business Information Services, short WhoBis is a service to check business informations like whois, Page Rank, Backlinks, Traffic and Keywords of Webpages and Companys

Visit whobis.com

Key Findings

We analyzed Whobis.com page load time and found that the first response time was 214 ms and then it took 480 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

whobis.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value3.9 s

89/100

10%

Network Requests Diagram

whobis.com

214 ms

first-style.css

91 ms

a

6 ms

s.gif

9 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 50% of them (2 requests) were addressed to the original Whobis.com, 25% (1 request) were made to Xslt.alexa.com and 25% (1 request) were made to Xsltcache.alexa.com. The less responsive or slowest element that took the longest time to load (214 ms) belongs to the original domain Whobis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 kB (66%)

Content Size

6.7 kB

After Optimization

2.3 kB

In fact, the total size of Whobis.com main page is 6.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 3.5 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 2.2 kB

  • Original 3.5 kB
  • After minification 3.2 kB
  • After compression 1.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 2.2 kB or 62% of the original size.

JavaScript Optimization

-69%

Potential reduce by 2.2 kB

  • Original 3.2 kB
  • After minification 2.2 kB
  • After compression 972 B

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 2.2 kB or 69% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

whobis.com accessibility score

86

Accessibility Issues

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

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Best Practices

whobis.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whobis.com SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whobis.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Whobis.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

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