C — https://kiplinger.com | BeaverCheck Audit

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Alpine.js · 87 peers

You 70

Avg 77

-7 below average

0 50 100

Better than 2% of Alpine.js sites See full Alpine.js benchmark →

Amazon Route 53 · 814 peers

You 70

Avg 72

At average

0 50 100

Better than 14% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

Cookie 'FTR_Cache_Status' is missing the Secure flag

Security gaps expose your site and users to attacks, eroding trust.

Security › Cookie Security

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fkiplinger.com)](https://beavercheck.com/results/8050f847-ad77-4d75-9407-0bde73b7c250)

HTML

<a href="https://beavercheck.com/results/8050f847-ad77-4d75-9407-0bde73b7c250"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkiplinger.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fkiplinger.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

4 critical 4 warning

8 barrier(s) likely increasing bounce by ~34%.

Speed (2)

Page takes 5.2s to load

+12% bounce

Users abandon at ~3s — you're 2.7s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 1.3s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (1)

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (2)

Severe layout shift during page load

+6% bounce

Users mis-click when content jumps — converting intent into frustration

Fix: Reserve space for images, ads, and embeds with explicit width/height

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (1)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

10 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€383 investment → €3,216/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +9990%

Investment

€383

4h · 5 findings

Monthly returns

€3,216 /mo

~€38,595 / year

Conversions recovered €3,216
Bandwidth savings €0.65

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€383

4.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,008 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+11 more

Bandwidth Waste

€0.65 /mo

8775.6 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~878 KB per page load
Saves €0.65/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.07 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

5.22 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

1.26 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.688

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.07 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

18.33 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.6875610000000001] map[score:0.687274] map[node:map[boundingRect:map[bottom:671 height:72 left:16 right:396 top:599 width:380] lhId:page-14-H2 nodeLabel:Which Was Worse: The 1979 or Today's Oil Crisis? path:1,HTML,1,BODY,10,DIV,0,DIV,0,DIV,2,UL,0,LI,0,A,1,DIV,0,H2 selector:li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > h2.wdn-listv2-item-content-title snippet:<h2 class="wdn-listv2-item-content-title"> type:node] score:0.000287 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/merriweather/v33/u-4t0qyriQwlOrhSvowK_l5UcA6ht3ZEqezpPbXEE55RlL_FB7E.woff2]]] type:subitems]]]

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:90.222 source:map[type:text value:[unattributed]]] map[reflowTime:7.916 source:map[column:222 line:0 type:source-location url:https://www.kiplinger.com/vite/assets/Flexi/Widgets/Carouzelize.ts-BQCnpvGa.js urlProvider:network]]]

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
Alexandra Svokos in a striped blouse with a purple background. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/thicKegFQsZjAcN332CSxE-768-80.jpg.webp	84.6 KiB	81.8 KiB
headshot `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/8UyQuDSkz4xXJaPT2v47m8-768-80.jpg.webp	49.1 KiB	45.9 KiB
Alexandra Twin `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/MrAj5dYwYLuJcCQEHXQSdQ-768-80.jpg.webp	33.6 KiB	32.7 KiB
Man taking photo of happy multi-generational family on yacht with a smartphone `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/WgvJqsZkBxtVEom2rzkUTm-768-80.jpg.webp	49.3 KiB	31.6 KiB
Family with two kids eating dinner in restaurant and paying with smartphone `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/MJCMbtxmpFxbGTTWHtqaG6-768-80.jpg.webp	33.7 KiB	30.8 KiB
photo of author Kate Schubel `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/UgDuYP78MP6HLZCTuj6wpR-768-80.jpg.webp	32.1 KiB	29.9 KiB
Author profile pic `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/utrHE6sjywN2sZPLdAuC5Z-768-80.jpg.webp	27.3 KiB	25.9 KiB
Abstract light trails that look like they're in a tunnel. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/ZVzqVBQYhS4MKdF2x9ckBM-768-80.jpg.webp	25.5 KiB	23.3 KiB
David Dittman, investing editor at Kiplinger.com `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/atntNFPM5sSSnaYvgwZoQ6-768-80.jpg.webp	24.9 KiB	22.9 KiB
A man in a suit stands at a gas station, trying to hitchhike in the 1970s. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-768-80.jpg.webp	27.8 KiB	19.8 KiB
Kelley Taylor `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/Me6i3GsivpFmdfzm4ekUoG-768-80.jpg.webp	19.4 KiB	17.9 KiB
Senior Couple Calculating Household Expenses and Reviewing Bills at Home `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/LYbGXCYw2JQfEkuChW6cje-768-80.jpg.webp	28.7 KiB	15.0 KiB
Rachael Green `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/TBsj5vge5PFS893QLtWChb-768-80.jpg.webp	15.3 KiB	14.2 KiB
Donna Fuscaldo `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/XDwi5gBeFpN2ByFsyuqXnJ-768-80.jpg.webp	11.0 KiB	4.5 KiB

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-9-IMG

nodeLabel: A man in a suit stands at a gas station, trying to hitchhike in the 1970s.

path: 1,HTML,1,BODY,10,DIV,0,DIV,0,DIV,2,UL,0,LI,0,A,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img

snippet: <img src="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-768-80.jpg.webp" alt="A man in a suit stands at a gas station, trying to hitchhike in the 1970s." class="v2-listing-image-img block-image-ads" srcset="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-1920-80.jpg 1920w…" sizes="(min-width: 1024px) 970px, 100vw" data-original-mos="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX.jpg" data-pin-media="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX.jpg" data-pin-nopin="true">

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
/css2?family=Merriweather:ital,opsz,wght@0,18..144,300..9...	2.4 KiB	825 ms
fonts.googleapis.com/css2?family=Bebas+Neue&display=swap	499 B	175 ms
search-api.fie.futurecdn.net/css/browser/master-f8e9977d/progressive.min.css	10.6 KiB	903 ms

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
bordeaux.futurecdn.net/bordeaux.js	0.0 ms	159.1 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	1800.0 s	64.9 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
static.myfinance.com/widget/myFinance.js	14400.0 s	40.7 KiB
freyr.futurecdn.net/freyr.js	0.0 ms	21.1 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	3600.0 s	24.4 KiB
champagne.futurecdn.net/champagne.js	0.0 ms	16.5 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=2262	3600.0 s	4.3 KiB
sb.scorecardresearch.com/internal-cs/default/beacon-and.js	86400.0 s	7.8 KiB
uk-script.dotmetrics.net/Scripts/ncs-script.js?v=362	0.0 ms	2.9 KiB
cdn.mos.cms.futurecdn.net/flexiimages/c9yj8luxnb1764668254.svg	0.0 ms	2.3 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.3 KiB
static.myfinance.com/widget/myFinance.css	14400.0 s	1.6 KiB
cdn.mos.cms.futurecdn.net/flexiimages/veeb7he4s21759850692.svg	0.0 ms	1.0 KiB
cdn.mos.cms.futurecdn.net/flexiimages/thdy2qcakl1759911177.svg	0.0 ms	993 B
/hit.gif?id=12362&url=https%3A%2F%2Fwww.kiplinger.com%2F&...	86400.0 s	1.2 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 751 ms

URL	Time Spent
kiplinger.com/	751 ms
www.kiplinger.com/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
	0.687
Which Was Worse: The 1979 or Today's Oil Crisis? `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > h2.wdn-listv2-item-content-title`	0.000

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 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 300 ms 505.3 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k0	165.9 KiB	83.3 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js	105.6 KiB	65.2 KiB
www.googletagmanager.com/gtag/js?id=G-6YXLE2F61G&cx=c&gtm=4e64k0	161.2 KiB	64.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WKPHNF6H&gtm=4e64k0	123.6 KiB	64.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	143.0 KiB	47.4 KiB
vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js	89.7 KiB	33.1 KiB
bordeaux.futurecdn.net/bordeaux.js	55.1 KiB	31.3 KiB
static.myfinance.com/widget/myFinance.js	39.9 KiB	26.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	64.6 KiB	23.8 KiB
www.kiplinger.com/vite/assets/vendor-DH-HcC7C.js	36.8 KiB	22.6 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/hawklinks.js	38.4 KiB	22.2 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	23.9 KiB	22.1 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	2.0 s	914 ms	0.0 ms
www.kiplinger.com/	1.0 s	241 ms	30 ms
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	550 ms	481 ms	40 ms
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	518 ms	467 ms	17 ms
bordeaux.futurecdn.net/bordeaux.js	214 ms	156 ms	52 ms
www.googletagmanager.com/gtag/js?id=G-6YXLE2F61G&cx=c&gtm=4e64k0	178 ms	143 ms	33 ms
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js	172 ms	117 ms	38 ms
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	143 ms	96 ms	1.2 ms
www.googletagmanager.com/gtm.js?id=GTM-WKPHNF6H&gtm=4e64k0	140 ms	107 ms	29 ms
sb.scorecardresearch.com/cs/10055482/beacon.js	138 ms	93 ms	1.8 ms
cdn.privacy-mgmt.com/unified/4.40.1/usnat-uspapi.090eccada574d39af6f8.bundle.js	134 ms	98 ms	35 ms
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k0	133 ms	78 ms	54 ms
/experimentsexperience/render?id=AC_FSwIfbTJQTucDLD2XZTrr...	132 ms	125 ms	0.2 ms
freyr.futurecdn.net/freyr.js	129 ms	109 ms	8.7 ms
slice.vanilla.futurecdn.net/13-4-20/js/externals.js	70 ms	60 ms	9.7 ms
static.myfinance.com/widget/myFinance.js	61 ms	49 ms	11 ms
cdn.privacy-mgmt.com/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js	55 ms	39 ms	15 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	3.5 s
Other	1.2 s
Style & Layout	502 ms
Script Parsing & Compilation	390 ms
Garbage Collection	209 ms
Parse HTML & CSS	203 ms
Rendering	55 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.3 KiB

URL	Transfer Size	Est Savings
@font-face { font-family: "Lato-fallback"; size-adjust: 97.38%; ascent-override: 98%; … } …	100.6 KiB	5.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/s/merriweather/v33/u-4t0qyriQwlOrhSvowK_l5UcA6ht3ZEqezpP...	178.2 KiB
www.kiplinger.com/	171.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k0	165.9 KiB
www.googletagmanager.com/gtag/js?id=G-6YXLE2F61G&cx=c&gtm=4e64k0	161.2 KiB
bordeaux.futurecdn.net/bordeaux.js	159.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	143.4 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js	142.0 KiB
www.googletagmanager.com/gtm.js?id=GTM-WKPHNF6H&gtm=4e64k0	123.7 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	91.2 KiB
vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js	90.4 KiB

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

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 29 user timings

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 590 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.navigation > div.navigation__container > div.navigation__burgerbar > button.button-menu `nav.navigation > div.navigation__container > div.navigation__burgerbar > button.button-menu`
div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search `div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search`

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.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`
div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-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
footer#document-footer > section.max-w-screen-xl > nav.flex > a.inline-block `footer#document-footer > section.max-w-screen-xl > nav.flex > a.inline-block`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__submit-input `div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__submit-input`
STATE TAX `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
TAX LAW `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
RETIREMENT TAXES `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
TOOLS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
TOOLS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
ECONOMIC FORECASTS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
ECONOMIC FORECASTS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
THE KIPLINGER LETTER `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
THE KIPLINGER LETTER `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`

These are opportunities to improve the legibility of your content.

○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

●Input buttons have discernible text.

●Form elements have associated labels

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

●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

●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.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

○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 type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<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

○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

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
Unload event listeners are deprecated and will be removed.	bordeaux.futurecdn.net/bordeaux.js line 31, col 6976

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
cache.pythia.futureplc.com/v1alpha1/decision-engine/match_all	`Failed to load resource: the server responded with a status of 404 ()`
www.kiplinger.com/ line 11036, col 27	`TypeError: Cannot read properties of undefined (reading 'articleTemplate') at https://www.kiplinger.com/:11037:28`
vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js line 11, col 8687	`TypeError: Cannot read properties of undefined (reading 'length') at dd.generateCampaignsFromMatchAllResponse (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:12:8688) at dd.<anonymous> (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:12:8289) at Generator.next (<anonymous>) at i (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:1:502)`

●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

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●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

○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.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`
div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.07 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.69 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

31 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.204

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.29 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.69 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

items: [map[node:map[type:text value:Total] score:0.203667] map[node:map[boundingRect:map[bottom:0 height:0 left:0 right:0 top:0 width:0] lhId:page-18-META nodeLabel:head > meta path:1,HTML,0,HEAD,2,META selector:head > meta snippet:<meta name="viewport" content="width=device-width,initial-scale=1"> type:node] score:0.203667]]

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

items: [map[reflowTime:91.745 source:map[type:text value:[unattributed]]]]

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
Alexandra Svokos in a striped blouse with a purple background. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/thicKegFQsZjAcN332CSxE-1600-80.jpg.webp	285.9 KiB	282.2 KiB
headshot `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/8UyQuDSkz4xXJaPT2v47m8-1600-80.jpg.webp	147.2 KiB	143.0 KiB
Family with two kids eating dinner in restaurant and paying with smartphone `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/MJCMbtxmpFxbGTTWHtqaG6-1600-80.jpg.webp	134.1 KiB	128.9 KiB
Man taking photo of happy multi-generational family on yacht with a smartphone `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/WgvJqsZkBxtVEom2rzkUTm-1600-80.jpg.webp	131.1 KiB	125.9 KiB
Senior Couple Calculating Household Expenses and Reviewing Bills at Home `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/LYbGXCYw2JQfEkuChW6cje-1600-80.jpg.webp	77.8 KiB	72.1 KiB
https://cdn.mos.cms.futurecdn.net/hwgJ7osrMtUWhk5koeVme7-200-80.png `div.navigation__burgerbar > a.vanilla-blueconic-header-wrapper > div#blueconic-header-kiplinger > img.vanilla-blueconic-header__img`	cdn.mos.cms.futurecdn.net/hwgJ7osrMtUWhk5koeVme7-200-80.png	67.7 KiB	67.1 KiB
A mature couple at a cafe using credit card perks. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/MbNKqDuWvXtXWPZqqWMQe9-1024-80.jpg.webp	61.3 KiB	55.6 KiB
Abstract light trails that look like they're in a tunnel. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/ZVzqVBQYhS4MKdF2x9ckBM-1600-80.jpg.webp	49.7 KiB	47.7 KiB
Mature couple looking at laptop sitting outside at a cafe. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/j7V65nXAgrFMpxjTyZctdW-600-80.jpg.webp	51.1 KiB	45.5 KiB
Rachael Green `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/TBsj5vge5PFS893QLtWChb-1600-80.jpg.webp	41.9 KiB	40.7 KiB
Alexandra Twin `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/MrAj5dYwYLuJcCQEHXQSdQ-1600-80.jpg.webp	33.6 KiB	32.0 KiB
photo of author Kate Schubel `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/UgDuYP78MP6HLZCTuj6wpR-1600-80.jpg.webp	32.1 KiB	28.5 KiB
Author profile pic `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/utrHE6sjywN2sZPLdAuC5Z-1600-80.jpg.webp	27.3 KiB	25.0 KiB
David Dittman, investing editor at Kiplinger.com `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/atntNFPM5sSSnaYvgwZoQ6-1600-80.jpg.webp	24.9 KiB	21.5 KiB
A man in a suit stands at a gas station, trying to hitchhike in the 1970s. `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-1024-80.jpg.webp	38.9 KiB	18.5 KiB
Kelley Taylor `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/Me6i3GsivpFmdfzm4ekUoG-1600-80.jpg.webp	19.4 KiB	16.9 KiB
A woman in her eighties or nineties looks out the window from the driver's side… `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/QccCzCb3SxBVrtKJwwhAYb-600-80.jpg.webp	16.3 KiB	13.9 KiB
Donna Fuscaldo `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`	cdn.mos.cms.futurecdn.net/XDwi5gBeFpN2ByFsyuqXnJ-1600-80.jpg.webp	11.0 KiB	4.5 KiB

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-14-IMG

nodeLabel: A man in a suit stands at a gas station, trying to hitchhike in the 1970s.

path: 1,HTML,1,BODY,10,DIV,0,DIV,0,DIV,2,UL,0,LI,0,A,0,DIV,0,DIV,0,PICTURE,1,IMG

selector: div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img

snippet: <img src="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-1024-80.jpg.webp" alt="A man in a suit stands at a gas station, trying to hitchhike in the 1970s." class="v2-listing-image-img block-image-ads" srcset="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX-1920-80.jpg 1920w…" sizes="(min-width: 1024px) 970px, 100vw" data-original-mos="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX.jpg" data-pin-media="https://cdn.mos.cms.futurecdn.net/8gsBNW2HDiJzTxByoqeQWX.jpg" data-pin-nopin="true">

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.

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

value: No additional origins are good candidates for preconnecting

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
bordeaux.futurecdn.net/bordeaux.js	0.0 ms	159.1 KiB
cdn.privacy-mgmt.com/Notice.8f529.js	3600.0 s	91.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	1800.0 s	64.9 KiB
cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js	3600.0 s	42.0 KiB
static.myfinance.com/widget/myFinance.js	14400.0 s	40.7 KiB
freyr.futurecdn.net/freyr.js	0.0 ms	21.2 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	3600.0 s	24.4 KiB
champagne.futurecdn.net/champagne.js	0.0 ms	16.5 KiB
cdn.privacy-mgmt.com/Notice.30929.css	3600.0 s	6.7 KiB
sdk.mrf.io/statics/compass-multimedia-sdk.js?version=2262	3600.0 s	4.3 KiB
uk-script.dotmetrics.net/Scripts/ncs-script.js?v=362	0.0 ms	2.9 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js	86400.0 s	6.7 KiB
cdn.mos.cms.futurecdn.net/flexiimages/c9yj8luxnb1764668254.svg	0.0 ms	2.4 KiB
cdn.privacy-mgmt.com/polyfills.01516.js	3600.0 s	2.3 KiB
static.myfinance.com/widget/myFinance.css	14400.0 s	1.6 KiB
cdn.mos.cms.futurecdn.net/flexiimages/thdy2qcakl1759911177.svg	0.0 ms	993 B
/hit.gif?id=12362&url=https%3A%2F%2Fwww.kiplinger.com%2F&...	86400.0 s	1.2 KiB

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
/css2?family=Merriweather:ital,opsz,wght@0,18..144,300..9...	2.0 KiB	271 ms
fonts.googleapis.com/css2?family=Bebas+Neue&display=swap	870 B	63 ms
search-api.fie.futurecdn.net/css/browser/master-f8e9977d/progressive.min.css	10.6 KiB	235 ms

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 242 ms

URL	Time Spent
kiplinger.com/	242 ms
www.kiplinger.com/	0.0 ms

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
head > meta `head > meta`	0.204

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

Diagnostics

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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 50 ms 588.6 KiB

URL	Transfer Size	Est Savings
bordeaux.futurecdn.net/bordeaux.js	158.6 KiB	90.5 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js	140.0 KiB	86.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k0	165.9 KiB	83.3 KiB
www.googletagmanager.com/gtag/js?id=G-6YXLE2F61G&cx=c&gtm=4e64k0	161.2 KiB	65.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WKPHNF6H&gtm=4e64k0	123.6 KiB	65.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	143.0 KiB	47.4 KiB
vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js	89.7 KiB	33.3 KiB
static.myfinance.com/widget/myFinance.js	39.9 KiB	26.2 KiB
sdk.mrf.io/statics/marfeel-sdk.js?id=7842	64.6 KiB	23.8 KiB
www.kiplinger.com/vite/assets/vendor-DH-HcC7C.js	36.8 KiB	22.7 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/hawklinks.js	38.4 KiB	22.2 KiB
sdk.mrf.io/statics/47bd3e88b6bda15c34ce.js	23.9 KiB	22.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.3 KiB

URL	Transfer Size	Est Savings
@font-face { font-family: "Lato-fallback"; size-adjust: 97.38%; ascent-override: 98%; … } …	100.6 KiB	5.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
cdn.mos.cms.futurecdn.net/thicKegFQsZjAcN332CSxE-1600-80.jpg.webp	286.8 KiB
/s/merriweather/v33/u-4t0qyriQwlOrhSvowK_l5UcA6ht3ZEqezpP...	178.2 KiB
www.kiplinger.com/	171.2 KiB
www.googletagmanager.com/gtm.js?id=GTM-WHLXGS3C&gtm=4e64k0	165.9 KiB
www.googletagmanager.com/gtag/js?id=G-6YXLE2F61G&cx=c&gtm=4e64k0	161.2 KiB
bordeaux.futurecdn.net/bordeaux.js	159.1 KiB
cdn.mos.cms.futurecdn.net/8UyQuDSkz4xXJaPT2v47m8-1600-80.jpg.webp	148.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWBWRXL	143.4 KiB
search-api.fie.futurecdn.net/js/w/es6/master-f8e9977d/progressive.js	142.0 KiB
cdn.mos.cms.futurecdn.net/WHoXDm9NSDeGtNaNfAZCWW-1600-80.jpg.webp	140.7 KiB

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

●Max Potential First Input Delay 80 ms

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Reduce unused CSS

●User Timing marks and measures 29 user timings

●JavaScript execution time 0.8 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 5 long tasks found

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

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 530 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid non-composited animations

Accessibility

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search `div.navigation__container > div.navigation__burgerbar > div.search > button.navigation__search`

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.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`
div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.navigation__second-tier > ul.navigation__groupitems > li.navigation__item > a.navigation__link `div.navigation__second-tier > ul.navigation__groupitems > li.navigation__item > a.navigation__link`
footer#document-footer > section.max-w-screen-xl > nav.flex > a.inline-block `footer#document-footer > section.max-w-screen-xl > nav.flex > a.inline-block`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__submit-input `div.newsletter-form__container > section.newsletter-form__main-section > form.newsletter-form__form > input.form__submit-input`
TOOLS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
TOOLS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
ECONOMIC FORECASTS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
ECONOMIC FORECASTS `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
THE KIPLINGER LETTER `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`
THE KIPLINGER LETTER `li.wdn-listv2-item > a.wdn-listv2-item-link > div.wdn-listv2-item-content > span.wdn-listv2-item-content-title-label`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NEWSLETTER `div.navigation__container > div.navigation__topitem > div.social > li.social__item`

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

●Input buttons have discernible text.

●Form elements have associated labels

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

●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

●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.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●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

○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 type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○`<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

○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

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
Unload event listeners are deprecated and will be removed.	bordeaux.futurecdn.net/bordeaux.js line 31, col 6976

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
cache.pythia.futureplc.com/v1alpha1/decision-engine/match_all	`Failed to load resource: the server responded with a status of 404 ()`
www.kiplinger.com/ line 11036, col 27	`TypeError: Cannot read properties of undefined (reading 'articleTemplate') at https://www.kiplinger.com/:11037:28`
vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js line 11, col 8687	`TypeError: Cannot read properties of undefined (reading 'length') at dd.generateCampaignsFromMatchAllResponse (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:12:8688) at dd.<anonymous> (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:12:8289) at Generator.next (<anonymous>) at i (https://vanilla.futurecdn.net/kiplinger/app.Cl0pY1ep.js:1:502)`

●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

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●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

○Mitigate clickjacking with XFO or CSP

SEO

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.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img`
div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-img `div.v2-listing-image-layout > div.v2-listing-image-wrapper > picture > img.v2-listing-image-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

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://kiplinger.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (1)

Usability (2)

Content (1)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Contrast

Tables and lists

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts