Tools & Wizards About Us
whobegatwhom.co.uk screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

whobegatwhom.co.uk

Family History of Philip Wilson. Family trees and genealogy. 5000+ records

Page Load Speed

3.1 sec in total

First Response

392 ms

Resources Loaded

2.3 sec

Page Rendered

370 ms

whobegatwhom.co.uk screenshot

About Website

Welcome to whobegatwhom.co.uk homepage info - get ready to check Whobegatwhom best content right away, or after learning these important things about whobegatwhom.co.uk

Share family history + genealogy. Ancestry of many families: Hurlock, Murray, Elibank, Badnall, Hopkins, Fiennes, Clifford, Bassett, Ingham, Cruso, etc.

Visit whobegatwhom.co.uk

Key Findings

We analyzed Whobegatwhom.co.uk page load time and found that the first response time was 392 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

whobegatwhom.co.uk performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

36/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.178

68/100

15%

TTI (Time to Interactive)

Value7.2 s

51/100

10%

Network Requests Diagram

whobegatwhom.co.uk

392 ms

fhstyle.css

331 ms

lytebox.js

440 ms

lytebox.css

214 ms

style.css

443 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Whobegatwhom.co.uk, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Whobegatwhom.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 296.1 kB (11%)

Content Size

2.6 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whobegatwhom.co.uk main page is 2.6 MB. 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. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 52.1 kB

  • Original 69.4 kB
  • After minification 67.9 kB
  • After compression 17.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 52.1 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 80.3 kB

  • Original 2.3 MB
  • After minification 2.2 MB

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. Whobegatwhom images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 47.2 kB

  • Original 76.4 kB
  • After minification 64.0 kB
  • After compression 29.2 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 47.2 kB or 62% of the original size.

CSS Optimization

-91%

Potential reduce by 116.5 kB

  • Original 127.4 kB
  • After minification 110.1 kB
  • After compression 10.9 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. Whobegatwhom.co.uk needs all CSS files to be minified and compressed as it can save up to 116.5 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (5%)

Requests Now

58

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whobegatwhom.co.uk

whobegatwhom.co.uk

392 ms

fhstyle.css

fhstyle.css

331 ms

lytebox.js

lytebox.js

440 ms

lytebox.css

lytebox.css

214 ms

style.css

style.css

443 ms

analytics.js

analytics.js

36 ms

css

css

66 ms

collect

collect

163 ms

Murray%20motto%20brooch%20small%20logo%20version.jpg

Murray%20motto%20brooch%20small%20logo%20version.jpg

152 ms

collect

collect

93 ms

Website%20composite%20new.jpg

Website%20composite%20new.jpg

519 ms

alexander_4th_lord_elibank_2.jpg

alexander_4th_lord_elibank_2.jpg

174 ms

elizabeth_rushworth.jpg

elizabeth_rushworth.jpg

254 ms

a_margaret_martin_nee_french.jpg

a_margaret_martin_nee_french.jpg

266 ms

alexander_murray_17121778,_jacobite_1742_by_allan_ramsay.jpg

alexander_murray_17121778,_jacobite_1742_by_allan_ramsay.jpg

230 ms

anna_burnet.jpg

anna_burnet.jpg

429 ms

anne_clifford.jpg

anne_clifford.jpg

311 ms

anne_fitzgerald.jpg

anne_fitzgerald.jpg

369 ms

bassett_26_2.jpg

bassett_26_2.jpg

427 ms

bertie_murray_maybe_2.jpg

bertie_murray_maybe_2.jpg

460 ms

edward_iii_a.jpg

edward_iii_a.jpg

468 ms

eleanor_of_aquitaine.jpg

eleanor_of_aquitaine.jpg

485 ms

1st_lord_arniston.jpg

1st_lord_arniston.jpg

543 ms

emily_hurlock__onez__probably.jpg

emily_hurlock__onez__probably.jpg

647 ms

emily_mabel_girlie_nee_waller_martin.jpg

emily_mabel_girlie_nee_waller_martin.jpg

741 ms

ezekiel_hopkins_portrait.jpg

ezekiel_hopkins_portrait.jpg

612 ms

florence_may_badnell.jpg

florence_may_badnell.jpg

609 ms

frances_clifford_clifton.jpg

frances_clifford_clifton.jpg

647 ms

george_murray,_6th_lord_elibank.jpg

george_murray,_6th_lord_elibank.jpg

707 ms

gideon_murray_1.jpg

gideon_murray_1.jpg

789 ms

hezekiah_frith_17631848.jpg

hezekiah_frith_17631848.jpg

776 ms

hopkins_badnall_3_2.jpg

hopkins_badnall_3_2.jpg

776 ms

iris_wilson_1.jpg

iris_wilson_1.jpg

776 ms

james_murray__theophile_hamel.jpg

james_murray__theophile_hamel.jpg

855 ms

john_stewart,_1st_earl_oftraquhair.jpg

john_stewart,_1st_earl_oftraquhair.jpg

867 ms

john_wilson_and_seacroft_hall_c_186070.jpg

john_wilson_and_seacroft_hall_c_186070.jpg

879 ms

margaret_martin_nee_french_2.jpg

margaret_martin_nee_french_2.jpg

913 ms

maurice_fiennes_fitzgerald_wilson.jpg

maurice_fiennes_fitzgerald_wilson.jpg

913 ms

maurice_fitzgerald_wilson_2.jpg

maurice_fitzgerald_wilson_2.jpg

936 ms

mrs._waller_mother_of_emily_mabel.jpg

mrs._waller_mother_of_emily_mabel.jpg

1015 ms

muriel_10.jpg

muriel_10.jpg

993 ms

patrick_murray_5th_elibank.jpg

patrick_murray_5th_elibank.jpg

1000 ms

paul_bw_1.jpg

paul_bw_1.jpg

1042 ms

peter_fiennes_wilson_2.jpg

peter_fiennes_wilson_2.jpg

1064 ms

phil_may_photograph.jpg

phil_may_photograph.jpg

1085 ms

js

js

79 ms

cs-ctrl-basic.woff

cs-ctrl-basic.woff

1019 ms

richard_badnall_jnr.jpg

richard_badnall_jnr.jpg

965 ms

richard_badnall_snr.jpg

richard_badnall_snr.jpg

913 ms

richard_bassett_wilson_2.jpg

richard_bassett_wilson_2.jpg

922 ms

richard_bassett_wilson_of_cliffe_hall_died_march1869.jpg

richard_bassett_wilson_of_cliffe_hall_died_march1869.jpg

937 ms

samuel_saltus_ingham_jnr.jpg

samuel_saltus_ingham_jnr.jpg

900 ms

sir_robert_holmes_right.jpg

sir_robert_holmes_right.jpg

865 ms

thomas_charles_martin_father_of_charlie.jpg

thomas_charles_martin_father_of_charlie.jpg

823 ms

thomas_robins_bolitho_on_barum.jpg

thomas_robins_bolitho_on_barum.jpg

875 ms

william_herbert_1st_earl_of_pembroke__2nd.jpg

william_herbert_1st_earl_of_pembroke__2nd.jpg

886 ms

william_the_conqueror.jpg

william_the_conqueror.jpg

903 ms

james_ii_of_scotland.jpg

james_ii_of_scotland.jpg

872 ms

PW%20signature%20small.jpg

PW%20signature%20small.jpg

872 ms

Whobegatwhom%20link%20to%20Photonomy%20image%202.5%20inches%20wide.jpg

Whobegatwhom%20link%20to%20Photonomy%20image%202.5%20inches%20wide.jpg

880 ms

Accessibility Review

whobegatwhom.co.uk accessibility score

72

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

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

whobegatwhom.co.uk best practices score

75

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

whobegatwhom.co.uk SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Whobegatwhom.co.uk 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 Whobegatwhom.co.uk 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

whobegatwhom.co.uk

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