2.2 sec in total
280 ms
1.5 sec
410 ms
Visit 100in100.findmypast.com.au now to see the best up-to-date 100 In Findmypast content for Australia and also check out these interesting facts you probably never knew about 100in100.findmypast.com.au
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.com.auWe analyzed 100in100.findmypast.com.au page load time and found that the first response time was 280 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
100in100.findmypast.com.au performance score
name
value
score
weighting
Value1.8 s
89/100
10%
Value1.8 s
98/100
25%
Value6.5 s
39/100
10%
Value4,640 ms
0/100
30%
Value0
100/100
15%
Value17.3 s
4/100
10%
280 ms
1141 ms
36 ms
23 ms
17 ms
Our browser made a total of 57 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.au, 63% (36 requests) were made to D3nd02ak4v4ued.cloudfront.net and 19% (11 requests) were made to Images.prismic.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Findmypast.com.au.
Page size can be reduced by 405.9 kB (16%)
2.5 MB
2.1 MB
In fact, the total size of 100in100.findmypast.com.au main page is 2.5 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. 75% 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. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 212.2 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 212.2 kB or 83% of the original size.
Potential reduce by 1.3 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 192.0 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.0 kB or 15% 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.au 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 33 (65%)
51
18
The browser has sent 51 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 34 to 1 for JavaScripts and as a result speed up the page load time.
100in100.findmypast.com.au
280 ms
www.findmypast.com.au
1141 ms
ueu8cey.css
36 ms
p.css
23 ms
tp.widget.bootstrap.min.js
17 ms
router.6ce474ee9e90ac8d2d93.css
19 ms
app.795f0e6ddf8a3a4f8699.js
80 ms
vendors-node_modules_reach_utils_compose-event-handlers_dist_reach-utils-compose-event-handle-8aac23.56cc8d4b4cbec64c3a6e.js
44 ms
vendors-node_modules_reach_dialog_dist_reach-dialog_cjs_prod_js-node_modules_lodash_cloneDeep-5781a8.cb24ef072584957516ed.js
52 ms
vendors-node_modules_reach_combobox_dist_reach-combobox_cjs_prod_js-node_modules_reach_combob-92a4a8.6222d1a679fc5f2173b6.js
44 ms
vendors-node_modules_emotion_is-prop-valid_dist_emotion-is-prop-valid_esm_js-node_modules_int-401df1.56433f5c7b9a20f3dc3c.js
87 ms
services_app_packages_entitlements_src_common_features_js-services_app_packages_entitlements_-a91bbe.80e5c961cdc74654c50d.js
45 ms
services_app_packages_entitlements_src_components_entitlement-wrapper_jsx-services_app_packag-bde507.d5b74ce08fa83325f5b9.js
60 ms
services_canopy_packages_forms_src_input_jsx.9aaf8c385f573528a472.js
60 ms
services_app_packages_helmets_src_meta-theme_jsx-services_app_packages_shared-hooks_src_ecomm-46fe20.265c08437b28332f63bc.js
61 ms
router.81ea6cc0f5b9d6d27d8e.js
86 ms
home-logged-out.7ee63ca1c36a75e2c1fd.js
86 ms
vendors-node_modules_prismic-reactjs_dist_prismic-reactjs_js.1ccf089985fbca071610.js
85 ms
vendors-node_modules_lodash_assignWith_js-node_modules_lodash_difference_js-node_modules_loda-bdec9d.99072660f32ebaa6fdf5.js
93 ms
services_app_packages_ui-field-mapping_src_regions_js.f0188a1a0a4e260ad7c4.js
96 ms
services_canopy_packages_icons_src_buttons_list-icon_jsx-services_canopy_packages_icons_src_r-5b8eaa.410176493bd364ca3fcf.js
95 ms
services_app_packages_search-url-state_src_from-location_from-location_js-services_app_packag-0f7c89.da4194fa3875fcfb512a.js
94 ms
services_app_packages_home_src_common-components_search-tile_utilities_search-url-builder_js--35609c.8639208dd65560e71d1b.js
94 ms
services_app_packages_home_src_common-components_quick-links_index_jsx-services_app_packages_-e859a5.2cf01961038dc303de80.js
95 ms
services_app_packages_prismic_src_utils_jsx-services_app_packages_search-url-state_src_new-pa-22611f.53a1195247b3825ec68d.js
98 ms
other-partnerships-homepage.585774f23447fec1dc70.js
98 ms
vendors-node_modules_prop-types_prop-types_js.f829f04b4b37e4c15b43.js
99 ms
vendors-node_modules_date-fns_addHours_index_js-node_modules_date-fns_addMinutes_index_js-nod-87446d.81e7b9560c1b12abcabc.js
99 ms
vendors-node_modules_date-fns_index_js.7f8b52a3f77a6ddfe149.js
100 ms
services_app_packages_ecomm-utils_src_checkout-event-tracker_jsx.1d2fe8ce12cdc5e68bde.js
101 ms
services_canopy_packages_icons_src_actions_add-icon_jsx-services_canopy_packages_overlay_src_-11d698.5fc3b95cf39512cc9505.js
100 ms
services_canopy_packages_navigation_src_navbar_jsx-services_canopy_packages_tree-core_src_per-f5b562.122aaac7b5aee7b48604.js
101 ms
services_app_packages_errors_src_error-boundary_jsx-services_app_packages_freemium_src_hooks_-be7afb.b8712b19a95b2cf0d704.js
102 ms
services_app_packages_layout_src_navbar_index_js.f65cb3a1f928232df74f.js
105 ms
services_app_packages_layout_src_footer_jsx.6f1dce1f4d594727e276.js
102 ms
layout.2c11a113006e191bba79.js
107 ms
old-browser-notification.8d6cd5c558623f1d3eb5.js
102 ms
maintenance-banner-wrapper.d801b9db513e2180d055.js
105 ms
gtm.js
137 ms
a5fb39f3-5fd5-495e-9e98-b56fdf2b7515_fmp-1440x470-aus-210722.jpg
104 ms
573820ac1f65c5476128ac4e5c8bbe2e.svg
81 ms
8c4986ee4828b47d16f5cd694ef065f2.svg
88 ms
9459d55def6995f694f2c6a4fd01c4a8.svg
85 ms
c46c5ccd-ab3c-491b-a181-14c3ba0e45de_fmp-750x750-aus-uk-270722.jpg
89 ms
20a5967c-8eba-48cc-a19a-7d1e034d44ac_fmp-750x750-280622-02.png
90 ms
cab44b1a-afbd-4e79-89c5-481f170ab0ce_fmp-750x750-280622-03.png
99 ms
f6323422-2bfd-4ea8-beab-cad43807eb96_fmp-750x750-280622-04.png
105 ms
1f3c003d-0a9c-4959-8220-da9b8b549dc7_fmp-750x750-280622-05.png
101 ms
79bb50d9-0494-4cd5-ac4d-1e0fa8c58373_fmp-750x750-280622-06.png
98 ms
f0c6f343-5429-42d0-80c3-dac4e558a3f7_fmp-750x750-280622-07.png
105 ms
1b9afa16-cbcf-4d1c-8d9b-29ae9996dbef_search-records-icon.png
100 ms
7fdd547b-d294-4de3-a0b8-3a68c0303198_fmp-750x750-aus-130722.png
100 ms
ebaa5ffc-9b24-4113-8b8f-8c804d786928_icon-leaf-750x750.png
105 ms
d
23 ms
d
39 ms
d
39 ms
d
40 ms
100in100.findmypast.com.au 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.au 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
Missing source maps for large first-party JavaScript
100in100.findmypast.com.au 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.au 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.au 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.au
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: