Tools & Wizards About Us
british-genealogy.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

british-genealogy.com

British Genealogy & Family History Forums

Page Load Speed

5.3 sec in total

First Response

53 ms

Resources Loaded

4.1 sec

Page Rendered

1.2 sec

british-genealogy.com screenshot

About Website

Visit british-genealogy.com now to see the best up-to-date British Genealogy content for United Kingdom and also check out these interesting facts you probably never knew about british-genealogy.com

FREE UK Family History Forums, Genealogy Forums & Ancestry Community

Visit british-genealogy.com

Key Findings

We analyzed British-genealogy.com page load time and found that the first response time was 53 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

british-genealogy.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value6.5 s

38/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

british-genealogy.com

53 ms

british-genealogy.com

394 ms

417 ms

css

35 ms

jquery-3.4.1.min.js

21 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 62% of them (41 requests) were addressed to the original British-genealogy.com, 9% (6 requests) were made to Google-analytics.com and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain British-genealogy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (56%)

Content Size

2.2 MB

After Optimization

953.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of British-genealogy.com main page is 2.2 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 382.8 kB

  • Original 428.2 kB
  • After minification 390.3 kB
  • After compression 45.4 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 382.8 kB or 89% of the original size.

Image Optimization

-50%

Potential reduce by 815.2 kB

  • Original 1.6 MB
  • After minification 800.0 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. Obviously, British Genealogy needs image optimization as it can save up to 815.2 kB or 50% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 620 B

  • Original 104.3 kB
  • After minification 104.3 kB
  • After compression 103.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. This website has mostly compressed JavaScripts.

CSS Optimization

-11%

Potential reduce by 570 B

  • Original 5.0 kB
  • After minification 5.0 kB
  • After compression 4.5 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. British-genealogy.com needs all CSS files to be minified and compressed as it can save up to 570 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (78%)

Requests Now

59

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

british-genealogy.com

british-genealogy.com

53 ms

british-genealogy.com

british-genealogy.com

394 ms

417 ms

css

css

35 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

21 ms

jquery-migrate-3.1.0.min.js

jquery-migrate-3.1.0.min.js

22 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

218 ms

connection-min.js

connection-min.js

222 ms

vbulletin-core.js

vbulletin-core.js

487 ms

css.php

css.php

479 ms

bg_2019.css

bg_2019.css

441 ms

css.php

css.php

441 ms

css.php

css.php

177 ms

vbulletin_md5.js

vbulletin_md5.js

416 ms

cookieControl-5.1.min.js

cookieControl-5.1.min.js

180 ms

navbit-home.png

navbit-home.png

10 ms

collapse_40b.png

collapse_40b.png

439 ms

forum_old_lock-48.png

forum_old_lock-48.png

439 ms

icon1.png

icon1.png

100 ms

lastpost-right.png

lastpost-right.png

152 ms

icon5.png

icon5.png

456 ms

icon4.png

icon4.png

395 ms

icon6.png

icon6.png

537 ms

category_forum_old_lock-48.png

category_forum_old_lock-48.png

792 ms

subforum_old-48.png

subforum_old-48.png

770 ms

subforum_old.png

subforum_old.png

806 ms

poll_posticon.gif

poll_posticon.gif

822 ms

icon7.png

icon7.png

853 ms

users_online.png

users_online.png

891 ms

forum_stats.png

forum_stats.png

1169 ms

legend.png

legend.png

1182 ms

forum_new-16.png

forum_new-16.png

1204 ms

forum_old-16.png

forum_old-16.png

1201 ms

category-16.png

category-16.png

1251 ms

forum_link-16.png

forum_link-16.png

1311 ms

cron.php

cron.php

1672 ms

gtm.js

gtm.js

153 ms

gtm.js

gtm.js

232 ms

forum_header.png

forum_header.png

1571 ms

navigation.jpg

navigation.jpg

1210 ms

black_downward_arrow.png

black_downward_arrow.png

1597 ms

fwr_searchform.php

fwr_searchform.php

1300 ms

search.jpg

search.jpg

1549 ms

row.jpg

row.jpg

1621 ms

title.jpg

title.jpg

1248 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

66 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

117 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

118 ms

analytics.js

analytics.js

99 ms

fbevents.js

fbevents.js

135 ms

ga.js

ga.js

66 ms

ga.js

ga.js

85 ms

ga.js

ga.js

117 ms

collect

collect

67 ms

collect

collect

21 ms

collect

collect

65 ms

__utm.gif

__utm.gif

66 ms

js

js

59 ms

__utm.gif

__utm.gif

100 ms

js

js

99 ms

__utm.gif

__utm.gif

82 ms

1845 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

3 ms

british-genealogy-banner-960x90.jpg

british-genealogy-banner-960x90.jpg

685 ms

358 ms

Accessibility Review

british-genealogy.com accessibility score

78

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

british-genealogy.com best practices score

67

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

SEO Factors

british-genealogy.com SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise British-genealogy.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 British-genealogy.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

british-genealogy.com

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