1.9 sec in total
312 ms
1.3 sec
247 ms
Click here to check amazing 100 In Findmypast content for United States. Otherwise, check out these important facts you probably never knew about 100in100.findmypast.com
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.comWe analyzed 100in100.findmypast.com page load time and found that the first response time was 312 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
100in100.findmypast.com performance score
name
value
score
weighting
Value1.8 s
88/100
10%
Value2.6 s
87/100
25%
Value7.2 s
30/100
10%
Value4,740 ms
0/100
30%
Value0
100/100
15%
Value17.4 s
4/100
10%
312 ms
911 ms
43 ms
41 ms
44 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 100in100.findmypast.com, 75% (36 requests) were made to D3nd02ak4v4ued.cloudfront.net and 10% (5 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (911 ms) relates to the external source Findmypast.com.
Page size can be reduced by 385.1 kB (23%)
1.7 MB
1.3 MB
In fact, the total size of 100in100.findmypast.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 192.7 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 192.7 kB or 83% of the original size.
Potential reduce by 0 B
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 192.1 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 192.1 kB or 14% of the original size.
Potential reduce by 374 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. 100in100.findmypast.com needs all CSS files to be minified and compressed as it can save up to 374 B or 13% of the original size.
Number of requests can be reduced by 34 (81%)
42
8
The browser has sent 42 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 35 to 1 for JavaScripts and as a result speed up the page load time.
100in100.findmypast.com
312 ms
www.findmypast.com
911 ms
ueu8cey.css
43 ms
tp.widget.bootstrap.min.js
41 ms
router.6ce474ee9e90ac8d2d93.css
44 ms
p.css
25 ms
app.65c2cb233c17130a7fa2.js
51 ms
vendors-node_modules_reach_utils_compose-event-handlers_dist_reach-utils-compose-event-handle-8aac23.56cc8d4b4cbec64c3a6e.js
28 ms
vendors-node_modules_reach_dialog_dist_reach-dialog_cjs_prod_js-node_modules_lodash_cloneDeep-5781a8.cb24ef072584957516ed.js
32 ms
vendors-node_modules_reach_combobox_dist_reach-combobox_cjs_prod_js-node_modules_reach_combob-92a4a8.6222d1a679fc5f2173b6.js
31 ms
vendors-node_modules_emotion_is-prop-valid_dist_emotion-is-prop-valid_esm_js-node_modules_int-401df1.56433f5c7b9a20f3dc3c.js
51 ms
services_app_packages_entitlements_src_common_features_js-services_app_packages_entitlements_-a91bbe.80e5c961cdc74654c50d.js
31 ms
services_app_packages_entitlements_src_components_entitlement-wrapper_jsx-services_app_packag-bde507.d5b74ce08fa83325f5b9.js
39 ms
services_canopy_packages_forms_src_input_jsx.9aaf8c385f573528a472.js
44 ms
services_app_packages_helmets_src_meta-theme_jsx-services_app_packages_shared-hooks_src_ecomm-46fe20.265c08437b28332f63bc.js
45 ms
router.341a976963509992201f.js
51 ms
home-logged-out.7ee63ca1c36a75e2c1fd.js
49 ms
vendors-node_modules_prismic-reactjs_dist_prismic-reactjs_js.1ccf089985fbca071610.js
51 ms
vendors-node_modules_lodash_assignWith_js-node_modules_lodash_difference_js-node_modules_loda-bdec9d.99072660f32ebaa6fdf5.js
51 ms
services_app_packages_ui-field-mapping_src_regions_js.f0188a1a0a4e260ad7c4.js
54 ms
services_canopy_packages_icons_src_buttons_list-icon_jsx-services_canopy_packages_icons_src_r-5b8eaa.410176493bd364ca3fcf.js
57 ms
services_app_packages_search-url-state_src_from-location_from-location_js-services_app_packag-0f7c89.da4194fa3875fcfb512a.js
56 ms
services_app_packages_home_src_common-components_search-tile_utilities_search-url-builder_js--35609c.8639208dd65560e71d1b.js
51 ms
services_app_packages_home_src_common-components_quick-links_index_jsx-services_app_packages_-e859a5.2cf01961038dc303de80.js
55 ms
services_app_packages_prismic_src_utils_jsx-services_app_packages_search-url-state_src_new-pa-22611f.53a1195247b3825ec68d.js
53 ms
other-partnerships-homepage.585774f23447fec1dc70.js
57 ms
vendors-node_modules_prop-types_prop-types_js.f829f04b4b37e4c15b43.js
58 ms
vendors-node_modules_date-fns_addHours_index_js-node_modules_date-fns_addMinutes_index_js-nod-87446d.81e7b9560c1b12abcabc.js
58 ms
vendors-node_modules_date-fns_index_js.7f8b52a3f77a6ddfe149.js
60 ms
services_app_packages_ecomm-utils_src_checkout-event-tracker_jsx.1d2fe8ce12cdc5e68bde.js
59 ms
services_canopy_packages_icons_src_actions_add-icon_jsx-services_canopy_packages_overlay_src_-11d698.5fc3b95cf39512cc9505.js
61 ms
services_canopy_packages_navigation_src_navbar_jsx-services_canopy_packages_tree-core_src_per-f5b562.122aaac7b5aee7b48604.js
60 ms
services_app_packages_errors_src_error-boundary_jsx-services_app_packages_freemium_src_hooks_-be7afb.b8712b19a95b2cf0d704.js
62 ms
services_app_packages_layout_src_navbar_index_js.f65cb3a1f928232df74f.js
68 ms
services_app_packages_layout_src_footer_jsx.6f1dce1f4d594727e276.js
62 ms
layout.2c11a113006e191bba79.js
67 ms
old-browser-notification.8d6cd5c558623f1d3eb5.js
63 ms
maintenance-banner-wrapper.d801b9db513e2180d055.js
65 ms
gtm.js
129 ms
e10f88a7-d6ca-431c-a04e-93cc45d59b2b_us-hero.jpg
56 ms
573820ac1f65c5476128ac4e5c8bbe2e.svg
55 ms
d
30 ms
d
41 ms
d
42 ms
d
57 ms
8c4986ee4828b47d16f5cd694ef065f2.svg
37 ms
client.js
76 ms
9459d55def6995f694f2c6a4fd01c4a8.svg
27 ms
100in100.findmypast.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
100in100.findmypast.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
100in100.findmypast.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 100in100.findmypast.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 100in100.findmypast.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.
100in100.findmypast.com
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: