4.2 sec in total
120 ms
2.6 sec
1.4 sec
Welcome to enroll.23andme.com homepage info - get ready to check Enroll 23andMe best content for United States right away, or after learning these important things about enroll.23andme.com
23andMe offers DNA testing with the most comprehensive ancestry breakdown, personalized health insights and more.
Visit enroll.23andme.comWe analyzed Enroll.23andme.com page load time and found that the first response time was 120 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
enroll.23andme.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value4.6 s
34/100
25%
Value20.1 s
0/100
10%
Value28,500 ms
0/100
30%
Value0
100/100
15%
Value39.0 s
0/100
10%
120 ms
41 ms
73 ms
89 ms
109 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Enroll.23andme.com, 24% (32 requests) were made to S.amazon-adsystem.com and 4% (6 requests) were made to Match.adsrvr.org. The less responsive or slowest element that took the longest time to load (740 ms) relates to the external source Google.com.
Page size can be reduced by 171.2 kB (52%)
330.0 kB
158.7 kB
In fact, the total size of Enroll.23andme.com main page is 330.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 187.6 kB which makes up the majority of the site volume.
Potential reduce by 154.8 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 154.8 kB or 83% of the original size.
Potential reduce by 388 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. Obviously, Enroll 23andMe needs image optimization as it can save up to 388 B or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 15.8 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 15.8 kB or 13% of the original size.
Potential reduce by 271 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. Enroll.23andme.com has all CSS files already compressed.
Number of requests can be reduced by 100 (85%)
117
17
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enroll 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 44 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.23andme.com
120 ms
27075387.js
41 ms
c154e5fa78f10c24bcf2.css
73 ms
65e5a0137780f88e24e7.css
89 ms
5b86098390f1b3e92047.css
109 ms
8669557dbf9ff9a70cf5.css
98 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
156 ms
403.ead764f6e0223696fd4e.js
72 ms
webpack-82667b420d1ffa2e50e2.js
106 ms
framework-e12e56e0b8a76d261551.js
154 ms
main-47124985a1a012f637ea.js
152 ms
_app-0dc0249187f96e45ba40.js
190 ms
9062-1fcc7bfb28f3624569b7.js
191 ms
5675-323a35cca5a347c91c96.js
240 ms
8777-a0197557d320b3935e04.js
239 ms
642-322d9b944b8fac6bf0b0.js
244 ms
2466-e4d9eed43e1e9427d797.js
243 ms
7648-72e89f6c8b260cd93f73.js
245 ms
7008-d30416a34d1a94472a40.js
245 ms
8633-9e24199b0fff1df8fe9e.js
247 ms
8206-db4643c8cf9e14498c25.js
246 ms
1158-d3e0be992160258059f6.js
248 ms
3997-59dcc5cf3970136b5b0e.js
249 ms
5539-b299559c200ca03c1a15.js
252 ms
index-b773e83f1c323387e706.js
250 ms
_buildManifest.js
250 ms
_ssgManifest.js
251 ms
heap-244557998.js
35 ms
gtm.js
114 ms
light-blue-heart.svg
317 ms
green-apple.svg
321 ms
yellow-check.svg
315 ms
red-shoe.svg
318 ms
stacked-headline.svg
218 ms
subtext.svg
230 ms
caret-down-gray7.svg
229 ms
conversion_async.js
202 ms
analytics.js
264 ms
core.js
315 ms
pixel.js
358 ms
uwt.js
357 ms
scevent.min.js
300 ms
TC-3239-1.gif
292 ms
343 ms
fbevents.js
289 ms
bat.js
288 ms
airpr.js
287 ms
pop-up-shop.js
131 ms
bk-coretag.js
367 ms
activityi;src=9214610;type=pagev0;cat=gmp-u005;ord=7067981070560;gtm=2wga30;auiddc=945763041.1664920727;~oref=https%3A%2F%2Fwww.23andme.com%2F
248 ms
316 ms
311 ms
78 ms
collect
59 ms
210 ms
iu3
85 ms
308315429350550
62 ms
main.3a217bc7.js
58 ms
rp.gif
407 ms
adsct
435 ms
adsct
508 ms
pr
94 ms
504 ms
486 ms
446 ms
cookie_sync
461 ms
z
425 ms
pixel
530 ms
v2
456 ms
TC-3673-1.gif
423 ms
user-registering
466 ms
520 ms
660 ms
740 ms
src=9214610;type=pagev0;cat=gmp-u005;ord=7067981070560;gtm=2wga30;auiddc=945763041.1664920727;~oref=https%3A%2F%2Fwww.23andme.com%2F
111 ms
120 ms
ecm3
106 ms
ecm3
219 ms
ecm3
261 ms
ecm3
309 ms
ecm3
308 ms
ecm3
277 ms
ecm3
276 ms
ecm3
300 ms
px
363 ms
quant.js
345 ms
cirt_v2.min.js
371 ms
pixel
363 ms
px
361 ms
ecm3
302 ms
px
389 ms
ecm3
281 ms
xuid
227 ms
ecm3
273 ms
ecm3
301 ms
ecm3
361 ms
ecm3
309 ms
ecm3
308 ms
ecm3
304 ms
ecm3
302 ms
ecm3
219 ms
ecm3
218 ms
ecm3
217 ms
ecm3
215 ms
ecm3
170 ms
ecm3
151 ms
ecm3
150 ms
ecm3
149 ms
ecm3
148 ms
ecm3
147 ms
ecm3
147 ms
ecm3
111 ms
ecm3
108 ms
rules-p-Q_fnG13J2gNXs.js
84 ms
pixel
45 ms
pixie.js
137 ms
cnv
49 ms
pixel
48 ms
rubicon
129 ms
pixel
102 ms
match-result
82 ms
match-result
27 ms
generic
10 ms
appnexus
13 ms
src=11413669;type=invmedia;cat=23and0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=1
28 ms
generic
9 ms
pixel
31 ms
generic
8 ms
rum
19 ms
11 ms
collect
73 ms
92661
211 ms
ct.html
83 ms
4538
97 ms
enroll.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
enroll.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
Page has valid source maps
enroll.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 Enroll.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 Enroll.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.
enroll.23andme.com
Open Graph data is detected on the main page of Enroll 23andMe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: