Tools & Wizards About Us
whowhatwhereresearch.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

whowhatwhereresearch.com

Family History, Genealogy, Family Tree, Ancestors - based Chiswick west London 07917 863794 gill.thomas@whowhatwhereresearch.com

Page Load Speed

2.9 sec in total

First Response

554 ms

Resources Loaded

2.2 sec

Page Rendered

110 ms

whowhatwhereresearch.com screenshot

About Website

Click here to check amazing Whowhatwhereresearch content. Otherwise, check out these important facts you probably never knew about whowhatwhereresearch.com

Website of Family Tree and Genealogy researchers Who? What? Where? Whether you are beginning to find out more about your Family History or need more advanced advice, we can help. We specialise in Wels...

Visit whowhatwhereresearch.com

Key Findings

We analyzed Whowhatwhereresearch.com page load time and found that the first response time was 554 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

whowhatwhereresearch.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.4 s

55/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.061

98/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

www.whowhatwhereresearch.com

554 ms

layout.css

108 ms

font.css

329 ms

web.css

440 ms

common,facebook,shoppingbasket

443 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 52% of them (14 requests) were addressed to the original Whowhatwhereresearch.com, 30% (8 requests) were made to Cdn.website-start.de and 7% (2 requests) were made to 106.sb.mywebsite-editor.com. The less responsive or slowest element that took the longest time to load (845 ms) relates to the external source Cdn.website-start.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.0 kB (17%)

Content Size

236.9 kB

After Optimization

195.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whowhatwhereresearch.com main page is 236.9 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. 20% of websites need less resources to load. Images take 147.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 19.8 kB

  • Original 27.4 kB
  • After minification 25.9 kB
  • After compression 7.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 19.8 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 1.8 kB

  • Original 147.9 kB
  • After minification 146.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. Whowhatwhereresearch images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 19.0 kB

  • Original 59.7 kB
  • After minification 59.7 kB
  • After compression 40.7 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 19.0 kB or 32% of the original size.

CSS Optimization

-20%

Potential reduce by 396 B

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 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. Whowhatwhereresearch.com needs all CSS files to be minified and compressed as it can save up to 396 B or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (65%)

Requests Now

26

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.whowhatwhereresearch.com

www.whowhatwhereresearch.com

554 ms

layout.css

layout.css

108 ms

font.css

font.css

329 ms

web.css

web.css

440 ms

common,facebook,shoppingbasket

common,facebook,shoppingbasket

443 ms

logstate2-css.php

logstate2-css.php

460 ms

logstate-js.php

logstate-js.php

474 ms

web.js

web.js

845 ms

web.bundle.js

web.bundle.js

447 ms

common,facebook,shoppingbasket

common,facebook,shoppingbasket

675 ms

701 ms

pfcsupport.js

pfcsupport.js

540 ms

emotionheader.jpg

emotionheader.jpg

246 ms

logo.jpg

logo.jpg

239 ms

header_overlay_left.png

header_overlay_left.png

107 ms

header_overlay_right.png

header_overlay_right.png

214 ms

menu_overlay.png

menu_overlay.png

321 ms

menu_bottom.jpg

menu_bottom.jpg

322 ms

column_bg.jpg

column_bg.jpg

328 ms

sub_menu.gif

sub_menu.gif

338 ms

cache_2493591624.png

cache_2493591624.png

362 ms

cache_2420267934.png

cache_2420267934.png

449 ms

facebook-share-icon.png

facebook-share-icon.png

497 ms

analytics.js

analytics.js

23 ms

printer.gif

printer.gif

104 ms

collect

collect

14 ms

js

js

58 ms

Accessibility Review

whowhatwhereresearch.com accessibility score

65

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

whowhatwhereresearch.com SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

whowhatwhereresearch.com

Open Graph data is detected on the main page of Whowhatwhereresearch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: