2.5 sec in total
160 ms
1.7 sec
711 ms
Visit 23andme.com now to see the best up-to-date 23andMe content for United States and also check out these interesting facts you probably never knew about 23andme.com
23andMe offers DNA testing with the most comprehensive ancestry breakdown, personalized health insights and more.
Visit 23andme.comWe analyzed 23andme.com page load time and found that the first response time was 160 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
23andme.com performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value3.0 s
79/100
25%
Value6.2 s
44/100
10%
Value4,460 ms
0/100
30%
Value0
100/100
15%
Value14.5 s
9/100
10%
160 ms
524 ms
116 ms
107 ms
114 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original 23andme.com, 57% (45 requests) were made to 23andme.https.internapcdn.net and 5% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (524 ms) belongs to the original domain 23andme.com.
Page size can be reduced by 1.6 MB (43%)
3.8 MB
2.1 MB
In fact, the total size of 23andme.com main page is 3.8 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. 50% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 76.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. This page needs HTML code to be minified as it can gain 24.4 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 76.6 kB or 80% of the original size.
Potential reduce by 48.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. 23andMe images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 70% of the original size.
Potential reduce by 206.7 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. 23andme.com needs all CSS files to be minified and compressed as it can save up to 206.7 kB or 82% of the original size.
Number of requests can be reduced by 40 (58%)
69
29
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 23andMe. 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 as a result speed up the page load time.
23andme.com
160 ms
www.23andme.com
524 ms
3DGwCDRyKZJ-3Dx32hyvdQ_ga_utils.js
116 ms
jquery.min.js
107 ms
nnAdDINTOs_ZIRozQTEG2Q_jquery-migrate-1.2.1.min.js
114 ms
27075387.js
318 ms
dpTH6k5fC7cPh_AqkGLh4g_lib.js
163 ms
S7-3h6-IuiHh8bbkvcI0MA_youpub.css
146 ms
eWFrqLhZ8unydHZ1u1Q-_A_public.js
78 ms
RXYPcSaBh8-qZBcfMOwfFA_veil.js
77 ms
nDbktrEaCOYMq8-ZyTXMrQ_common.js
77 ms
SX-BqGtQqYAMl8A5zO9WWA_reports.js
84 ms
event
74 ms
dc.js
143 ms
gtm.js
201 ms
tGtinAwK7iaDMQoJsLF2Eg_icn_logo.png
58 ms
vFpz17BPqtPAmX6BQaR1KQ_truste_seal.html
53 ms
NSoeJxUvc6fpzqMLFi4aPw_search_close.png
56 ms
UVj5GsDIeOg_xrcqyY0JQQ_icon-burger.svg
52 ms
eMSIv5E4y1ilKTq6zq1MEQ_logo.svg
54 ms
pbjLQjDImehjYwfS-MxTyQ_icon-x.svg
55 ms
3SzaNbDDf8qsNPLU5Hh30A_kit.png
248 ms
uL7P15hOmzmZtTR7ZNB3Jw_us_kit.png
57 ms
eXETdK-d_vgDbSBes4gYhw_chromo.png
192 ms
PZOmLN5c_R1Bxb5MP_1lAA_lab_chip.png
246 ms
tT38qzkGWdLIP3ZdixwaYw_difference_dashboard.png
107 ms
RBSp-MdTOoiSULJJ3k74Yw_tube.png
107 ms
QCeEofEvzd4U3NYoPqgSeQ_stories.png
302 ms
Sjz0ew3ZgvUjeXsGYT_3tA_faq-expand.svg
119 ms
R_TOK-r7A3XpH3Ay7okW9Q_kit-thumbnail.png
119 ms
O2XlHEn_heTgsB-O_Isn1g_icon-chevron-right.svg
124 ms
utieRI5BGSW2pOPodp85Qw_spit-kit.svg
128 ms
ql9NGnzIas00D7Bk0gBpjQ_ux-what-you-get.svg
185 ms
_wvUADxZMIEncBgEPgLxDg_science.svg
188 ms
oo3mBTOWresqwDqlhjk3Sg_important-info.svg
246 ms
vT5NIcljBsD24pc2glptjg_logo-facebook.svg
247 ms
V1lvGdB8TFb9kanIkuZgMw_logo-twitter.svg
248 ms
RbD_OFwNGiy1Y5GyVSXrvw_logo-google.svg
261 ms
wC-OsQwogln5KAwigsHWEg_logo-youtube.svg
259 ms
A_a4EjpMsyi-gAORi0l6KA_united_states_14_11.png
261 ms
8poDHpuAV6gFImwUqf-mCQ_icon-carrot-up.svg
261 ms
3Nx3kzNrx97Oad9Z5Ud4ZA_close-white.svg
258 ms
7c5FeP8D9TFLr4PeWbcH5g_united_states_32_32.png
302 ms
yhsg_PnKRHN6EG1TJnAJCQ_canada_32_32.png
299 ms
U_kc3Nm2naerU4R-11beQw_united_kingdom_32_32.png
299 ms
yrrRwqlYx0NMtUkCrAkUuQ_international.svg
300 ms
nXys7Au3YR5fH2N8V0gO0w_eu_32_32.png
299 ms
asc
185 ms
seal
197 ms
ovZvess55eL6fq3y86pG9A_1e9892c0-6927-4412-9874-1b82801ba47a.woff
289 ms
__LLh6RHgchC-6gDy-wLag_f26faddb-86cc-4477-a253-1e1287684336.woff
296 ms
KbgMiaEpiP9UBs2NdYtkAQ_91b50bbb-9aa1-4d54-9159-ec6f19d14a7c.woff
315 ms
YHUh1Jb13XM1ghcIiuzCeQ_b8e906a1-f5e8-4bf1-8e80-82c646ca4d5f.woff
296 ms
BFqdRt-3UDT8g8325APeXg_92b66dbd-4201-4ac2-a605-4d4ffc8705cc.woff
321 ms
ya8fGrxfb1ltnGC02yj6CA_conditions.json
150 ms
XlR4-X7obyWsj6Ohrntnbg_loadingAnimation.gif
161 ms
__utm.gif
139 ms
__utm.gif
131 ms
analytics.js
244 ms
conversion_async.js
238 ms
async_survey
278 ms
fbds.js
226 ms
5839d2e9-0bea-43f7-adc0-483cf91bdae3.js
257 ms
abandonment.js
344 ms
oct.js
270 ms
activityi;src=3781537;type=stand162;cat=23amh053;ord=6030654124613;~oref=https%3A%2F%2Fwww.23andme.com%2F
230 ms
ga-audiences
183 ms
118 ms
64 ms
linkid.js
28 ms
ec.js
44 ms
5839d2e9-0bea-43f7-adc0-483cf91bdae3.js
12 ms
WRf4.js
15 ms
prompt_embed_static.js
40 ms
20 ms
collect
14 ms
js
56 ms
46 ms
ga-audiences
41 ms
23andme.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
23andme.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
23andme.com 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
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 23andme.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 23andme.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.
23andme.com
Open Graph data is detected on the main page of 23andMe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: