2 sec in total
215 ms
1.3 sec
429 ms
Visit 100in100.findmypast.co.uk now to see the best up-to-date 100 In Findmypast content for United Kingdom and also check out these interesting facts you probably never knew about 100in100.findmypast.co.uk
Over 100 days, family history site findmypast is releasing and showcasing 100 record sets. From military records to births and deaths, they'll help you discover your ancestors. Whether they were war h...
Visit 100in100.findmypast.co.ukWe analyzed 100in100.findmypast.co.uk page load time and found that the first response time was 215 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
100in100.findmypast.co.uk performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.4 s
4/100
25%
Value5.9 s
47/100
10%
Value220 ms
88/100
30%
Value0
100/100
15%
Value9.0 s
33/100
10%
215 ms
1020 ms
43 ms
51 ms
51 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 100in100.findmypast.co.uk, 37% (22 requests) were made to D3nd02ak4v4ued.cloudfront.net and 32% (19 requests) were made to Images.prismic.io. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Findmypast.co.uk.
Page size can be reduced by 627.0 kB (13%)
4.7 MB
4.1 MB
In fact, the total size of 100in100.findmypast.co.uk main page is 4.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 550.6 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 550.6 kB or 77% of the original size.
Potential reduce by 19.2 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. 100 In Findmypast images are well optimized though.
Potential reduce by 57.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 57.2 kB or 11% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 26 (50%)
52
26
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 100 In Findmypast. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
100in100.findmypast.co.uk
215 ms
www.findmypast.co.uk
1020 ms
0c3fc12765fe112a.css
43 ms
fd9d1056-f5689264123f2d02.js
51 ms
8069-0693c44749929aca.js
51 ms
main-app-6baa95a8a38c155f.js
46 ms
8792-a2b15c5f0e4940b2.js
47 ms
3926-f62ebc482ecc3afc.js
48 ms
7456-553670d4259f2ea1.js
50 ms
global-error-9d64f328c3a771c9.js
51 ms
6107-d6247b3634d12840.js
50 ms
6810-1958f55e9f3e3dff.js
51 ms
7946-a26b3b2360fa8262.js
62 ms
9212-5a27a77d8e9f65a1.js
51 ms
292-3d319c496d02539c.js
65 ms
page-0ced5e8826c80b9b.js
62 ms
layout-dc449d7ff224fe15.js
61 ms
7793-1d2dca4359982369.js
61 ms
layout-fdd0842117c1e179.js
63 ms
error-fb1e08964df97d3c.js
66 ms
otSDKStub.js
67 ms
layout-4394438c6dfc6cbd.js
66 ms
polyfills-c67a75d1b6f99dc8.js
63 ms
css2
48 ms
ueu8cey.css
44 ms
1b38536b-0ffd-462f-82a3-7ad8ba0835ab.json
31 ms
p.css
27 ms
otBannerSdk.js
37 ms
ZmgmKJm069VX1oTO_desktop-left-hero.png
28 ms
ZmgWA5m069VX1oDn_hero-home-mobile.png
20 ms
ZmgmKJm069VX1oTN_desktop-right-hero.png
22 ms
dfcc65c9-fe10-431c-b7f1-f56dcc856839_tree-builder-desktop.png
23 ms
en.json
34 ms
otCenterRounded.json
32 ms
otPcTab.json
85 ms
ZmdcoJm069VX1nOX_newspaper-slice-graphic%402x.png
67 ms
trustpilot-5-stars-a8b3e.webp
26 ms
9071a6c2-d543-4c8c-af17-5b2ba77edf70_app-store.svg
92 ms
webpack-63d63c16a76cd03f.js
21 ms
Zmhor5m069VX1pJR_newspaper-slice-graphic%402x.png
93 ms
324ebe73-c5fc-4739-a2ad-47b6847e53d4_home-wendy-review.png
19 ms
054a482f-11cf-487f-9af0-403cc4eed675_home-speech-bubble-graphic.png
20 ms
35255761-0383-4538-bbab-c5b6619a77f4_home-david-review.png
89 ms
c0c0b5ec-c526-4270-bf14-c8e6c1ef3aff_home-geoffrey-review.png
89 ms
a9759694-0a2d-4f3d-9ad7-211f949d8794_tree-search-image-desktop.png
88 ms
ZnFFWJm069VX11JQ_free-trial-graphic.png
93 ms
840fb8f1-936c-4905-a6c0-ee377d683649_home-free-trial-graphic-desktop.png
91 ms
ZnKnVZm069VX135N_free-trial-graphic-tablet.png
96 ms
baa78d2d-d1eb-4a9c-9044-ee348ac298a3_tna.png
97 ms
41975ed5-1b17-451c-869a-9abc4fb110c3_partners-bl.png
94 ms
27570f42-f2c0-4fd2-9ca7-360eb06f164f_partners-fhf.png
96 ms
Zmmh85m069VX1rWa_homepage-help-slice-lg-desktop.png
97 ms
85af7765-1c5f-469b-8450-31a8ecd365df_help-slice-desktop.png
98 ms
19cb337f-2ba3-4a6b-968b-e11cc9b12cb8_play-store.svg
93 ms
d
18 ms
d
86 ms
d
86 ms
d
86 ms
d
37 ms
100in100.findmypast.co.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
100in100.findmypast.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Page has valid source maps
100in100.findmypast.co.uk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 100in100.findmypast.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 100in100.findmypast.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.
100in100.findmypast.co.uk
Open Graph data is detected on the main page of 100 In Findmypast. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: