5.2 sec in total
121 ms
3.5 sec
1.6 sec
Welcome to 23andmeforums.com homepage info - get ready to check 23andMe Forums best content for United States right away, or after learning these important things about 23andmeforums.com
23andMe offers DNA testing with the most comprehensive ancestry breakdown, personalized health insights and more.
Visit 23andmeforums.comWe analyzed 23andmeforums.com page load time and found that the first response time was 121 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
23andmeforums.com performance score
name
value
score
weighting
Value2.1 s
80/100
10%
Value2.7 s
86/100
25%
Value5.4 s
56/100
10%
Value1,440 ms
15/100
30%
Value0
100/100
15%
Value13.7 s
11/100
10%
121 ms
60 ms
173 ms
178 ms
162 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 23andmeforums.com, 23% (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 (907 ms) relates to the external source Analytics.twitter.com.
Page size can be reduced by 170.5 kB (52%)
325.0 kB
154.5 kB
In fact, the total size of 23andmeforums.com main page is 325.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. 70% of websites need less resources to load. HTML takes 187.5 kB which makes up the majority of the site volume.
Potential reduce by 154.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 154.7 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, 23andMe Forums 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.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 15.1 kB or 13% of the original size.
Potential reduce by 259 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. 23andmeforums.com has all CSS files already compressed.
Number of requests can be reduced by 101 (86%)
118
17
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 23andMe Forums. 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
121 ms
27075387.js
60 ms
c154e5fa78f10c24bcf2.css
173 ms
f71b1571a9bee5db9077.css
178 ms
59b2f9b9406cb6f824d3.css
162 ms
8669557dbf9ff9a70cf5.css
165 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
166 ms
403.ead764f6e0223696fd4e.js
164 ms
webpack-625790b6545cd9ad14e0.js
433 ms
framework-e12e56e0b8a76d261551.js
432 ms
main-47124985a1a012f637ea.js
428 ms
_app-e1ab27f3f12af9060d40.js
428 ms
7149-15702e3d4bdbacbecc02.js
426 ms
5675-323a35cca5a347c91c96.js
426 ms
8777-a0197557d320b3935e04.js
488 ms
642-322d9b944b8fac6bf0b0.js
487 ms
2466-e4d9eed43e1e9427d797.js
486 ms
7648-6cd1bc0e6986a61d1217.js
496 ms
7008-af7b8ad9dba25fe139af.js
443 ms
8633-9e24199b0fff1df8fe9e.js
491 ms
8206-db4643c8cf9e14498c25.js
494 ms
1158-d3e0be992160258059f6.js
497 ms
3997-59dcc5cf3970136b5b0e.js
496 ms
4752-69304f6126c170ce7d19.js
498 ms
index-09852c1e10ba3cb4d40e.js
592 ms
_buildManifest.js
585 ms
_ssgManifest.js
578 ms
heap-244557998.js
393 ms
gtm.js
446 ms
light-blue-heart.svg
501 ms
green-apple.svg
505 ms
yellow-check.svg
507 ms
red-shoe.svg
509 ms
stacked-headline.svg
428 ms
subtext.svg
287 ms
caret-down-gray7.svg
280 ms
h
222 ms
conversion_async.js
172 ms
analytics.js
305 ms
core.js
359 ms
pixel.js
401 ms
uwt.js
528 ms
scevent.min.js
515 ms
TC-3239-1.gif
380 ms
512 ms
fbevents.js
382 ms
bat.js
499 ms
airpr.js
454 ms
pop-up-shop.js
134 ms
bk-coretag.js
448 ms
activityi;src=9214610;type=pagev0;cat=gmp-u005;ord=2262017991091;gtm=2wg9s0;auiddc=1043578313.1664601346;~oref=https%3A%2F%2Fwww.23andme.com%2F
534 ms
513 ms
513 ms
171 ms
collect
103 ms
main.3a217bc7.js
132 ms
rp.gif
508 ms
308315429350550
174 ms
iu3
158 ms
849 ms
848 ms
843 ms
adsct
880 ms
adsct
907 ms
pr
204 ms
845 ms
mw
905 ms
cookie_sync
810 ms
z
713 ms
Serving
780 ms
v2
765 ms
Pug
797 ms
789 ms
TC-3673-1.gif
666 ms
791 ms
pixel
819 ms
750 ms
user-registering
872 ms
180 ms
src=9214610;type=pagev0;cat=gmp-u005;ord=2262017991091;gtm=2wg9s0;auiddc=1043578313.1664601346;~oref=https%3A%2F%2Fwww.23andme.com%2F
134 ms
ecm3
90 ms
ecm3
132 ms
ecm3
182 ms
ecm3
162 ms
xuid
161 ms
ecm3
237 ms
ecm3
226 ms
ecm3
248 ms
ecm3
245 ms
ecm3
245 ms
ecm3
240 ms
ecm3
240 ms
px
413 ms
quant.js
288 ms
cirt_v2.min.js
281 ms
pixel
236 ms
px
365 ms
px
287 ms
ecm3
269 ms
ecm3
281 ms
ecm3
279 ms
ecm3
278 ms
ecm3
255 ms
ecm3
342 ms
ecm3
344 ms
ecm3
342 ms
ecm3
340 ms
ecm3
342 ms
ecm3
307 ms
ecm3
305 ms
ecm3
327 ms
ecm3
325 ms
ecm3
320 ms
ecm3
317 ms
ecm3
316 ms
ecm3
317 ms
ecm3
239 ms
pixel
173 ms
pixie.js
198 ms
rules-p-Q_fnG13J2gNXs.js
208 ms
cnv
84 ms
pixel
63 ms
pixel
49 ms
match-result
72 ms
match-result
70 ms
pixel
18 ms
pixel
17 ms
12 ms
18 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
37 ms
rubicon
15 ms
generic
24 ms
rubicon
11 ms
rubicon
15 ms
rum
27 ms
rum
43 ms
collect
32 ms
92661
162 ms
ct.html
29 ms
4538
84 ms
23andmeforums.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
23andmeforums.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
Issues were logged in the Issues panel in Chrome Devtools
23andmeforums.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 23andmeforums.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 23andmeforums.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.
23andmeforums.com
Open Graph data is detected on the main page of 23andMe Forums. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: