Tools & Wizards About Us
ybase.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ybase.org

DNA Testing for Ancestry & Genealogy | FamilyTreeDNA

Page Load Speed

3.9 sec in total

First Response

41 ms

Resources Loaded

2.7 sec

Page Rendered

1.2 sec

ybase.org screenshot

About Website

Welcome to ybase.org homepage info - get ready to check Ybase best content right away, or after learning these important things about ybase.org

Discover your DNA story and unlock the secrets of your ancestry and genealogy with our autosomal DNA, Y-DNA, and mtDNA tests.

Visit ybase.org

Key Findings

We analyzed Ybase.org page load time and found that the first response time was 41 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

ybase.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value4,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

ybase.org

41 ms

www.familytreedna.com

933 ms

css

128 ms

css

123 ms

css

128 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ybase.org, 58% (61 requests) were made to Cms.familytreedna.com and 14% (15 requests) were made to Familytreedna.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Cms.familytreedna.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.9 kB (9%)

Content Size

2.7 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ybase.org main page is 2.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. 80% 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. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 103.0 kB

  • Original 129.9 kB
  • After minification 128.7 kB
  • After compression 26.9 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 103.0 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 116.6 kB

  • Original 2.5 MB
  • After minification 2.4 MB

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. Ybase images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 9.2 kB

  • Original 50.9 kB
  • After minification 50.9 kB
  • After compression 41.7 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 9.2 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (68%)

Requests Now

87

After Optimization

28

  • Images
  • JavaScript
  • CSS

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ybase. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ybase.org

ybase.org

41 ms

www.familytreedna.com

www.familytreedna.com

933 ms

css

css

128 ms

css

css

123 ms

css

css

128 ms

icon

icon

121 ms

materialdesignicons.min.css

materialdesignicons.min.css

120 ms

header

header

130 ms

eae.min.css

eae.min.css

278 ms

peel.css

peel.css

312 ms

v4-shims.min.css

v4-shims.min.css

333 ms

all.min.css

all.min.css

319 ms

vegas.min.css

vegas.min.css

260 ms

theme.min.css

theme.min.css

329 ms

header-footer.min.css

header-footer.min.css

328 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

321 ms

post-129.css

post-129.css

347 ms

swiper.min.css

swiper.min.css

375 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

357 ms

post-4505.css

post-4505.css

361 ms

css

css

114 ms

iconHelper.js

iconHelper.js

370 ms

jquery.min.js

jquery.min.js

371 ms

jquery-migrate.min.js

jquery-migrate.min.js

404 ms

css2

css2

112 ms

ftdna

ftdna

196 ms

optimize.js

optimize.js

137 ms

uc.js

uc.js

120 ms

widget-animated-headline.min.css

widget-animated-headline.min.css

437 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

376 ms

jquery

jquery

214 ms

collapsible-menu

collapsible-menu

144 ms

runtime

runtime

145 ms

polyfills

polyfills

299 ms

main

main

235 ms

runtime

runtime

179 ms

main

main

364 ms

tabbed-ancestry.css

tabbed-ancestry.css

435 ms

animations.min.css

animations.min.css

434 ms

eae.min.js

eae.min.js

436 ms

index.min.js

index.min.js

485 ms

v4-shims.min.js

v4-shims.min.js

438 ms

animated-main.min.js

animated-main.min.js

436 ms

particles.min.js

particles.min.js

485 ms

magnific.min.js

magnific.min.js

483 ms

vegas.min.js

vegas.min.js

558 ms

hello-frontend.min.js

hello-frontend.min.js

558 ms

ftdna-cart.js

ftdna-cart.js

558 ms

tabbed-ancestry.js

tabbed-ancestry.js

557 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

558 ms

webpack.runtime.min.js

webpack.runtime.min.js

557 ms

frontend-modules.min.js

frontend-modules.min.js

773 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

657 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

806 ms

wp-polyfill.min.js

wp-polyfill.min.js

656 ms

hooks.min.js

hooks.min.js

434 ms

i18n.min.js

i18n.min.js

572 ms

frontend.min.js

frontend.min.js

554 ms

waypoints.min.js

waypoints.min.js

535 ms

core.min.js

core.min.js

525 ms

frontend.min.js

frontend.min.js

794 ms

elements-handlers.min.js

elements-handlers.min.js

787 ms

mtDNA-box-1.png

mtDNA-box-1.png

674 ms

Family-Finder-box-1.png

Family-Finder-box-1.png

671 ms

Big-Y-box-1.png

Big-Y-box-1.png

673 ms

Y-DNA-box-1.png

Y-DNA-box-1.png

670 ms

Making-Connections-Video-Homepage-Wordpress-800-x-500-px-7.gif

Making-Connections-Video-Homepage-Wordpress-800-x-500-px-7.gif

1174 ms

person_a@2x.jpg

person_a@2x.jpg

783 ms

person_b@2x.jpg

person_b@2x.jpg

801 ms

person_c@2x.jpg

person_c@2x.jpg

784 ms

persona_a_card.svg

persona_a_card.svg

801 ms

hero-genealogy-diagram-3.svg

hero-genealogy-diagram-3.svg

656 ms

Hero-person-1.png

Hero-person-1.png

966 ms

persona_b_card.svg

persona_b_card.svg

784 ms

persona_c_card.svg

persona_c_card.svg

875 ms

Group-Projects.png

Group-Projects.png

883 ms

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

1-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

872 ms

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

2-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

871 ms

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

3-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

869 ms

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

4-icon-qivue8g0tkskoejb3mb6rzuv672jrww8l4de11q25w.png

879 ms

dna-secure-mobile@2x.webp

dna-secure-mobile@2x.webp

874 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

325 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

325 ms

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf

588 ms

KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf

KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf

598 ms

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf

601 ms

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf

598 ms

myorigins_map.webp

myorigins_map.webp

951 ms

myorigins_map_persona_1.webp

myorigins_map_persona_1.webp

827 ms

ftdna-brand.svg

ftdna-brand.svg

359 ms

Twitter.svg

Twitter.svg

405 ms

Facebook.svg

Facebook.svg

395 ms

Instagram.svg

Instagram.svg

396 ms

YouTube.svg

YouTube.svg

393 ms

pixel

pixel

411 ms

pixel

pixel

417 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

174 ms

KFOjCnqEu92Fr1Mu51TzBic6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsHYl4BO.ttf

36 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsHYl4BO.ttf

39 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsHYl4BO.ttf

38 ms

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

KFOkCnqEu92Fr1Mu51xIIzcXKMny.ttf

39 ms

KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsHYl4BO.ttf

147 ms

KFOiCnqEu92Fr1Mu51QrEzAdKuvwnYg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKuvwnYg.ttf

148 ms

api.min.js

api.min.js

180 ms

pixel

pixel

160 ms

pixel

pixel

94 ms

Accessibility Review

ybase.org accessibility score

66

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ybase.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

ybase.org SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ybase.org 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 Ybase.org 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.

Social Sharing Optimization

ybase.org

Open Graph data is detected on the main page of Ybase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: