Tools & Wizards About Us
whoishe.info screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

whoishe.info

Whoishe.info : Biography based encyclopedia.

Page Load Speed

3.2 sec in total

First Response

434 ms

Resources Loaded

2.7 sec

Page Rendered

145 ms

whoishe.info screenshot

About Website

Click here to check amazing Whoishe content for Turkey. Otherwise, check out these important facts you probably never knew about whoishe.info

Whoishe.info : Biography based encyclopedia.

Visit whoishe.info

Key Findings

We analyzed Whoishe.info page load time and found that the first response time was 434 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

whoishe.info performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

whoishe.info

434 ms

whoishe.info

611 ms

v1-all.css

289 ms

css

40 ms

all.js

399 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 70% of them (31 requests) were addressed to the original Whoishe.info, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Whoishe.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.2 kB (20%)

Content Size

543.5 kB

After Optimization

436.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whoishe.info main page is 543.5 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. 55% of websites need less resources to load. Javascripts take 307.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.9 kB

  • Original 43.2 kB
  • After minification 42.5 kB
  • After compression 9.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 33.9 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 4.9 kB

  • Original 149.7 kB
  • After minification 144.8 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. Whoishe images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 32.9 kB

  • Original 307.5 kB
  • After minification 307.0 kB
  • After compression 274.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.9 kB or 11% of the original size.

CSS Optimization

-82%

Potential reduce by 35.4 kB

  • Original 43.1 kB
  • After minification 38.5 kB
  • After compression 7.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. Whoishe.info needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

41

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoishe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

whoishe.info

whoishe.info

434 ms

whoishe.info

whoishe.info

611 ms

v1-all.css

v1-all.css

289 ms

css

css

40 ms

all.js

all.js

399 ms

v1-paging.css

v1-paging.css

429 ms

adsbygoogle.js

adsbygoogle.js

59 ms

platform.js

platform.js

29 ms

in.js

in.js

29 ms

analytics.js

analytics.js

63 ms

bg.jpg

bg.jpg

293 ms

sc_facebook.svg

sc_facebook.svg

146 ms

sc_twitter.svg

sc_twitter.svg

149 ms

sc_google.svg

sc_google.svg

273 ms

sc_pinterest.svg

sc_pinterest.svg

292 ms

sc_newsletter.svg

sc_newsletter.svg

407 ms

search_icon.svg

search_icon.svg

411 ms

logo_v3.png

logo_v3.png

437 ms

jackiechan-s.jpg

jackiechan-s.jpg

438 ms

antoniobanderas-s.jpg

antoniobanderas-s.jpg

439 ms

bradpitt-s.jpg

bradpitt-s.jpg

437 ms

charliechaplin-s.jpg

charliechaplin-s.jpg

540 ms

donaldtrump-s.jpg

donaldtrump-s.jpg

544 ms

robinwilliams-s.jpg

robinwilliams-s.jpg

581 ms

adriaenbrouwer-s.jpg

adriaenbrouwer-s.jpg

581 ms

allanmacleodcormack-s.jpg

allanmacleodcormack-s.jpg

582 ms

miyamotomusashi-s.jpg

miyamotomusashi-s.jpg

581 ms

morganfreeman-s.jpg

morganfreeman-s.jpg

674 ms

brad-pitt.jpg

brad-pitt.jpg

809 ms

tb_Keanu_Reeves_got_married_during_Dracula.jpg

tb_Keanu_Reeves_got_married_during_Dracula.jpg

725 ms

tb_George_Michael_has_died.jpg

tb_George_Michael_has_died.jpg

724 ms

tb_Russia_withdraws_signature_from_international_criminal_court_statute.jpg

tb_Russia_withdraws_signature_from_international_criminal_court_statute.jpg

726 ms

tb_Donald_Trump_Elected_45th_President_Of_The_United_States_Of_America.jpg

tb_Donald_Trump_Elected_45th_President_Of_The_United_States_Of_America.jpg

725 ms

ahcev8612zF4jxrwMosT6-xhgmy4.ttf

ahcev8612zF4jxrwMosT6-xhgmy4.ttf

64 ms

pu_menu.png

pu_menu.png

758 ms

collect

collect

66 ms

gray_bg.gif

gray_bg.gif

793 ms

sdk.js

sdk.js

51 ms

widgets.js

widgets.js

53 ms

js

js

75 ms

us_101.svg

us_101.svg

1015 ms

sdk.js

sdk.js

13 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

31 ms

settings

settings

70 ms

Accessibility Review

whoishe.info accessibility score

83

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whoishe.info best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whoishe.info 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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoishe.info 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 Whoishe.info 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

whoishe.info

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