Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
cadmus.script.ac/d1ppgmexmjm31c/script.js	600.0 s	87.6 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.2 KiB
c.amazon-adsystem.com/aax2/apstag.js	3600.0 s	90.9 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
rootsweb.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	11.9 KiB
01.cdn.mediatradecraft.com/rootsweb/main/main.js?template=homepage	76200.0 s	18.0 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.3 KiB
01.cdn.mediatradecraft.com/rootsweb/main/main.css	76200.0 s	2.7 KiB

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.552 source:map[column:26323 line:1 type:source-location url:https://01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.39 source:map[column:143834 line:0 type:source-location url:https://01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js urlProvider:network]] map[reflowTime:0.057 source:map[column:40493 line:0 type:source-location url:https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js urlProvider:network]] map[reflowTime:0.401 source:map[column:64052 line:0 type:source-location url:https://01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js urlProvider:network]] map[reflowTime:1.002 source:map[column:61089 line:0 type:source-location url:https://01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: div.conBody > div.homepageCard4Image > a > img

path: 1,HTML,1,BODY,7,DIV,0,DIV,0,DIV,1,SECTION,0,SECTION,0,DIV,1,DIV,0,A,0,IMG

selector: div.conBody > div.homepageCard4Image > a > img

snippet: <img src="https://www.ancestrycdn.com/aa-rw-home/86/images/rwHome/hosted.jpg">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.ancestrycdn.com/ui/2.18.0/js/core.js	24.8 KiB	151 ms
www.ancestrycdn.com/aa-rw-home/86/scripts/o3.js	638 B
/etc.clientlibs/ancestry/clientlibs/clientlib-base.min.AC...	65.9 KiB	2.6 s
www.ancestrycdn.com/ui-static/lib/jquery/1.11.1/jquery.min.js	29.5 KiB	756 ms
www.ancestrycdn.com/aa-rw-home/86/stylesheets/rwHome.css	1.3 KiB	151 ms
www.ancestrycdn.com/ui/2.10.0/css/core.css	18.8 KiB	756 ms
www.ancestrycdn.com/ui/2.18.0/css/core.css	19.3 KiB	454 ms
www.ancestrycdn.com/aa-rw-home/86/stylesheets/layout.css	1.1 KiB	781 ms

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.ancestrycdn.com/ui-static/font/source-sans-pro-bold.woff2	15 ms
www.ancestrycdn.com/ui-static/font/source-sans-pro.woff2	15 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/hosted.jpg	91.8 KiB	39.4 KiB
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/message.jpg	19.9 KiB	9.5 KiB
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/wiki-image.jpg	21.4 KiB	5.4 KiB

Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.

Why this matters

Performance issues directly impact user engagement and conversion rates.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 100 ms 100.9 KiB

URL	Transfer Size	Est Savings
/etc.clientlibs/ancestry/clientlibs/clientlib-base.min.AC...	65.2 KiB	64.7 KiB
www.ancestrycdn.com/ui/2.18.0/css/core.css	19.1 KiB	18.3 KiB
www.ancestrycdn.com/ui/2.10.0/css/core.css	18.6 KiB	18.0 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 4.3 s 666.1 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.7 KiB	131.3 KiB
cdn.ex.co/player/ap/4.230.0-947b4e1/player.js	138.6 KiB	114.9 KiB
micro.rubiconproject.com/prebid/dynamic/21666.js	152.3 KiB	105.9 KiB
player.ex.co/player/74f5c7b5-09b8-4b35-9a85-5637d4dae0c9	194.8 KiB	98.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-NSWCNL5	140.0 KiB	69.9 KiB
c.amazon-adsystem.com/aax2/apstag.js	90.4 KiB	57.8 KiB
01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js	40.7 KiB	23.8 KiB
cadmus.script.ac/d1ppgmexmjm31c/script.js	87.4 KiB	22.6 KiB
cdn.privacy-mgmt.com/unified/4.40.1/usnat.f12613136193900e32e2.bundle.js	42.0 KiB	21.4 KiB
www.ancestrycdn.com/ui-static/lib/jquery/1.11.1/jquery.min.js	29.2 KiB	20.4 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
Unattributable	409 ms	47 ms	0.0 ms
player.ex.co/player/74f5c7b5-09b8-4b35-9a85-5637d4dae0c9	335 ms	253 ms	54 ms
micro.rubiconproject.com/prebid/dynamic/21666.js	259 ms	223 ms	33 ms
01.cdn.mediatradecraft.com/cmdjs/runtime-2.8.16.js	250 ms	215 ms	16 ms
rootsweb.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	214 ms	204 ms	2.2 ms
rootsweb.com/	200 ms	72 ms	5.1 ms
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	176 ms	124 ms	46 ms
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	158 ms	127 ms	14 ms
www.googletagmanager.com/gtm.js?id=GTM-NSWCNL5	145 ms	117 ms	27 ms
cdn.ex.co/player/ap/4.230.0-947b4e1/player.js	141 ms	81 ms	59 ms
cdn.privacy-mgmt.com/unified/4.40.1/usnat.f12613136193900e32e2.bundle.js	121 ms	86 ms	35 ms
cadmus.script.ac/d1ppgmexmjm31c/script.js	108 ms	81 ms	24 ms
c.amazon-adsystem.com/aax2/apstag.js	108 ms	71 ms	28 ms
/static/js/25dd01c5/e8cedefce1bb90a47ead14b41f1a252e6e86d...	97 ms	74 ms	8.6 ms
securepubads.g.doubleclick.net/tag/js/gpt.js	85 ms	77 ms	7.5 ms
cdn.privacy-mgmt.com/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js	53 ms	37 ms	16 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	2.0 s
Other	403 ms
Script Parsing & Compilation	401 ms
Style & Layout	150 ms
Parse HTML & CSS	67 ms
Garbage Collection	61 ms
Rendering	11 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,817 KiB

●User Timing marks and measures 27 user timings

●Avoid long main-thread tasks 16 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 100 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 250 ms

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rwHeaderLeft > div.rwHeaderLogo > a > img `div.rwHeaderLeft > div.rwHeaderLogo > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rwHeaderWrapper > div.rwHeaderLeft > div.rwHeaderLogo > a `div.rwHeaderWrapper > div.rwHeaderLeft > div.rwHeaderLogo > a`
section.cardFourCard > div.conBody > div.homepageCard4Image > a `section.cardFourCard > div.conBody > div.homepageCard4Image > a`
section.cardFourCard > div.conBody > div.homepageCard4Image > a `section.cardFourCard > div.conBody > div.homepageCard4Image > a`
section.cardFourCard > div.conBody > div.homepageCard4Image > a `section.cardFourCard > div.conBody > div.homepageCard4Image > a`
section.cardFourCard > div.conBody > div.homepageCard4Image > a `section.cardFourCard > div.conBody > div.homepageCard4Image > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ancestry Newpapers.com Fold3 Find A Grave Ancestry Academy `div#featuredLinksGroup > div.ancGrid > div.ancCol > ul.inline`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/hosted.jpg	437 x 250 (1.75)	953 x 614 (1.55)
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/obituary.png	437 x 250 (1.75)	514 x 467 (1.10)
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/wiki-image.jpg	437 x 250 (1.75)	300 x 329 (0.91)
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/message.jpg	437 x 250 (1.75)	324 x 196 (1.65)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/message.jpg	437 x 250	324 x 196	656 x 375
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`	www.ancestrycdn.com/aa-rw-home/86/images/rwHome/wiki-image.jpg	437 x 250	300 x 329	656 x 375
div.rwHeaderLeft > div.rwHeaderLogo > a > img `div.rwHeaderLeft > div.rwHeaderLogo > a > img`	www.ancestrycdn.com/aa-rw-home/280/images/rw.gif	314 x 69	314 x 69	471 x 104

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	rootsweb.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	rootsweb.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	rootsweb.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.rwHeaderLeft > div.rwHeaderLogo > a > img `div.rwHeaderLeft > div.rwHeaderLogo > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`
div.conBody > div.homepageCard4Image > a > img `div.conBody > div.homepageCard4Image > a > img`

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

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid