C — https://triplinkintl.com

Site Health

Score: 76 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

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.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

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

Microsoft sites average 72

At average

Better than 80% of Microsoft sites See full Microsoft benchmark →

Open Graph sites average 74

At average

Better than 67% of Open Graph sites See full Open Graph benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

HSTS header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

No <main> landmark found

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

Accessibility › Landmark Structure

Soft 404: server returns HTTP 200 for non-existent pages

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

Accessibility › 404 Error Page

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%2Ftriplinkintl.com)](https://beavercheck.com/results/4e01ae50-c398-4853-a696-b222948f8ba5)

HTML

<a href="https://beavercheck.com/results/4e01ae50-c398-4853-a696-b222948f8ba5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftriplinkintl.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Ftriplinkintl.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

1 critical 6 warning

7 barrier(s) likely increasing bounce by ~26%.

Speed (2)

Page takes 10.0s to load

+12% bounce

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

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

High main-thread blocking time

+2% bounce

Page is non-interactive for 233ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

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 (1)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Content (1)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

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

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

Return on Investment

SGD 405 investment → SGD 7,171/month returns + SGD 1,000,000 risk avoided

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

Investment

SGD 405

4h · 5 findings

Monthly returns

SGD 7,171 /mo

~SGD 86,050 / year

Conversions recovered SGD 7,171
Bandwidth savings SGD 0.27

Regulatory risk avoided

SGD 1,000,000

if kept compliant

PDPA SGD 1,000,000

Payback period

0 12mo 24mo

SGD 135 — 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

S$405

4.5 developer hours at S$90/hr

Based on Singapore rates (S$90/hr)

Quick wins

S$135 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

S$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

SGD 83,334 / month at risk

~SGD 1,000,003 / year if left unfixed

Compliance Risk

SGD 1,000,000

PDPA

No privacy policy link detected
PDPA: SGD 10,000 – SGD 1,000,000
Trackers detected but no cookie policy found
PDPA: SGD 10,000 – SGD 1,000,000
Trackers detected but no privacy policy found
PDPA: SGD 10,000 – SGD 1,000,000

Bandwidth Waste

SGD 0.27 /mo

2499.4 MB/mo × 0.108 SGD/GB

Optimize transfer: save ~250 KB per page load
Saves SGD 0.27/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

100

Best Practices

100

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.

3.77 s

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

10.00 s

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

233 ms

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

0.155

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

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

10.03 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.154948] map[node:map[boundingRect:map[bottom:1464 height:585 left:0 right:412 top:879 width:412] lhId:page-1-SECTION nodeLabel:Global Leading Industry Solutions, bringing a brand new payment experience just… path:1,HTML,1,BODY,0,DIV,1,DIV,1,DIV,0,SECTION selector:div#__next > div > div.floor-hash__wrapper > section.tl-card-type__wrap snippet:<section class="tl-card-type__wrap"> type:node] score:0.136286 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:859 height:333 left:20 right:392 top:526 width:372] lhId:page-0-IMG nodeLabel:TripLik cards path:1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,SECTION,2,PICTURE,1,IMG selector:div.floor-hash__wrapper > section.tl-home-bannerv2__wrap > picture > img.wow snippet:<img loading="lazy" src="https://dimg04.tripcdn.com/images/1vf6112000ndkw4qq181C.webp" class="wow fadeInUp tl-home-bannerv2__img--h5" alt="TripLik cards" data-wow-duration="1s" data-wow-delay="300ms" data-wow-offset="0" data-wow-iteration="1" style="visibility: visible; animation-duration: 1s; animation-delay: 300ms;"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:1464 height:585 left:0 right:412 top:879 width:412] lhId:page-1-SECTION nodeLabel:Global Leading Industry Solutions, bringing a brand new payment experience just… path:1,HTML,1,BODY,0,DIV,1,DIV,1,DIV,0,SECTION selector:div#__next > div > div.floor-hash__wrapper > section.tl-card-type__wrap snippet:<section class="tl-card-type__wrap"> type:node] score:0.018662]]

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.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1373.2680009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:103.1199990234375 label:Resource load delay subpart:resourceLoadDelay] map[duration:1565.702 label:Resource load duration subpart:resourceLoadDuration] map[duration:25.363 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: TripLik cards

path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,SECTION,2,PICTURE,1,IMG

selector: div.floor-hash__wrapper > section.tl-home-bannerv2__wrap > picture > img.wow

snippet: <img loading="lazy" src="https://dimg04.tripcdn.com/images/1vf6112000ndkw4qq181C.webp" class="wow fadeInUp tl-home-bannerv2__img--h5" alt="TripLik cards" data-wow-duration="1s" data-wow-delay="300ms" data-wow-offset="0" data-wow-iteration="1" style="visibility: visible; animation-duration: 1s; animation-delay: 300ms;">

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: TripLik cards

path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,SECTION,2,PICTURE,1,IMG

selector: div.floor-hash__wrapper > section.tl-home-bannerv2__wrap > picture > img.wow

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.

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
/locale/v3/100031248/en-US.js?etagc=17a63344b256aefaffe72...	10.6 KiB	910 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
dimg04.tripcdn.com/images/1vf4v12000n6i0oi41A13.webp	1612322.0 s	23.3 KiB
dimg04.tripcdn.com/images/1vf1912000n85sazeE518.svg	1612321.0 s	15.3 KiB
dimg04.tripcdn.com/images/1vf5h12000n85slnuD8D7.svg	2362489.0 s	2.5 KiB
dimg04.tripcdn.com/images/1vf2712000n6i15ykF27E.webp	1301208.0 s	2.4 KiB
dimg04.tripcdn.com/images/1vf4512000nplra28D759.svg	2310362.0 s	2.0 KiB

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: 1.5 s

URL	Time Spent
triplinkintl.com/	1.5 s
www.triplinkintl.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
Global Leading Industry Solutions, bringing a brand new payment experience just… `div#__next > div > div.floor-hash__wrapper > section.tl-card-type__wrap`	0.136
Global Leading Industry Solutions, bringing a brand new payment experience just… `div#__next > div > div.floor-hash__wrapper > section.tl-card-type__wrap`	0.019

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 ▾

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: 1.2 s 213.9 KiB

URL	Transfer Size	Est Savings
/ares/NFES/100031248/1762236779672/_next/static/chunks/co...	206.8 KiB	180.9 KiB
/ares/NFES/100031248/1762236779672/_next/static/chunks/nf...	60.5 KiB	32.9 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
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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Our Awards 2x2 `div.floor-hash__wrapper > section.tl-honor__wrap > picture > img.wow`	dimg04.tripcdn.com/images/1vf0m12000f6g5uuqB97C.webp
TripLik cards `div.floor-hash__wrapper > section.tl-home-bannerv2__wrap > picture > img.wow`	dimg04.tripcdn.com/images/1vf6112000ndkw4qq181C.webp
TripLink card Global `section.tl-card-type__wrap > div.tl-card-type__content > picture > img.wow`	dimg04.tripcdn.com/images/1vf4v12000n6i0oi41A13.webp
TripLink office `div.floor-hash__wrapper > section.tl-business__wrap > picture > img.wow`	dimg04.tripcdn.com/images/1vf1p12000nscipj6D108.webp
TripLink Partners `section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__content > picture > img.wow`	dimg04.tripcdn.com/images/1vf1p12000n6i148e3A8E.webp
Employee Expense `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf2712000n6i15ykF27E.webp
Travel `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf1e12000n6i1cuy6A64.webp
Study Abroad `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf1n12000n6i0w9pBE45.webp
Amazon Ads `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf4e12000n6i0p4bD6DE.webp
TripLink light logo `section.tl-footer__floor > div.tl-footer__item > picture > img.tl-footer__logo`	dimg04.tripcdn.com/images/1vf0o12000djyrrtw8FA1.webp
by Trip.com `div.tl-header__wrapper > div.tl-header__content > a.tl-header__logo-wrapper > img.tl-header__logo-suffix`	dimg04.tripcdn.com/images/1vf5h12000n85slnuD8D7.svg
LinkedIn `ul > li.tl-footer__desc-content > a.tl-footer__desc-icon > img`	dimg04.tripcdn.com/images/1vf5z12000ndi3qrjCA45.svg

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

●Max Potential First Input Delay 130 ms

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 814 KiB

●User Timing marks and measures 4 user timings

●JavaScript execution time 1.0 s

●Minimizes main-thread work 1.9 s

●Avoid long main-thread tasks 7 long tasks found

●Network Requests

●Network Round Trip Times 260 ms

●Server Backend Latencies 580 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 550 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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cookie-banner-container > section.cookie-banner-words > div.cookie-banner-title > span.cookie-banner-expand `div.cookie-banner-container > section.cookie-banner-words > div.cookie-banner-title > span.cookie-banner-expand`

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.

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
Sign In `div.tl-header__wrapper > div.tl-header__content > div.tl-header__right > a.tl-login-btn`
Global `div.Dropdown-control > div.Dropdown-placeholder > div.siteAndLocale_item__R4JHA > span.siteAndLocale_text___w2yb`
English `div.Dropdown-control > div.Dropdown-placeholder > div.siteAndLocale_item__R4JHA > span.siteAndLocale_text___w2yb`
Links `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
Home `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Products `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Solutions `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
About Us `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
About Us `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Our Honour `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Privacy Policy `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Developers `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
API `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
SDK `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Contact us `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
E-mail: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
contact@triplinkintl.com `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Questions Feedback: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
triplinkceo@triplinkintl.com `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Shanghai: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
+86-21-34064880 `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Hong Kong: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
+852 58075570 `div.tl-footer__item > ul > li.tl-footer__desc-content > span`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Products `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Solutions `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
About Us `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Our Honour `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Privacy Policy `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
API `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
SDK `div.tl-footer__item > ul > li.tl-footer__desc-content > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

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

○Identical links have the same purpose.

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 browser errors logged to the console

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

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.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

100

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.84 s

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

2.99 s

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

0 ms

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

0.005

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

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

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

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.

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:34.683 source:map[type:text value:[unattributed]]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]

items: [map[duration:1899.4339990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:83.1440009765625 label:Resource load delay subpart:resourceLoadDelay] map[duration:30.253 label:Resource load duration subpart:resourceLoadDuration] map[duration:1552.189 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: TripLink VISA Card

path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,SECTION,1,DIV,0,PICTURE,1,IMG

selector: section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__bg > picture > img.wow

snippet: <img loading="lazy" src="https://dimg04.tripcdn.com/images/1vf3w12000qf0e93q41B5.webp" class="wow fadeInRight tl-home-bannerv2__img tl-home-bannerv2__img--bg1" alt="TripLink VISA Card" data-wow-duration="1s" data-wow-delay="300ms" data-wow-offset="0" data-wow-iteration="1" style="visibility: visible; animation-duration: 1s; animation-delay: 300ms;">

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: TripLink VISA Card

path: 1,HTML,1,BODY,0,DIV,1,DIV,0,DIV,0,SECTION,1,DIV,0,PICTURE,1,IMG

selector: section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__bg > picture > img.wow

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.

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

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
dimg04.tripcdn.com/images/1vf1p12000nscipj6D108.webp	1073550.0 s	81.9 KiB
dimg04.tripcdn.com/images/1vf3j12000ndkvycvB517.webp	1978242.0 s	32.6 KiB
dimg04.tripcdn.com/images/1vf3w12000qf0e93q41B5.webp	1710743.0 s	9.6 KiB
dimg04.tripcdn.com/images/1vf1p12000n6i148e3A8E.webp	1001719.0 s	3.6 KiB
dimg04.tripcdn.com/images/1vf1e12000n6i1cuy6A64.webp	1001720.0 s	2.5 KiB
dimg04.tripcdn.com/images/1vf1n12000n6i0w9pBE45.webp	2578741.0 s	2.3 KiB

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
/locale/v3/100031248/en-US.js?etagc=17a63344b256aefaffe72...	10.6 KiB	217 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: 1.1 s

URL	Time Spent
triplinkintl.com/	1.1 s
www.triplinkintl.com/	0.0 ms

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: 130 ms 213.8 KiB

URL	Transfer Size	Est Savings
/ares/NFES/100031248/1762236779672/_next/static/chunks/co...	206.8 KiB	180.9 KiB
/ares/NFES/100031248/1762236779672/_next/static/chunks/nf...	60.5 KiB	32.9 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
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

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Our Awards 4x1 `div.floor-hash__wrapper > section.tl-honor__wrap > picture > img.wow`	dimg04.tripcdn.com/images/1vf1c12000f6fadmu7EBA.webp
TripLink card Global `section.tl-card-type__wrap > div.tl-card-type__content > picture > img.wow`	dimg04.tripcdn.com/images/1vf4v12000n6i0oi41A13.webp
TripLink office `div.floor-hash__wrapper > section.tl-business__wrap > picture > img.wow`	dimg04.tripcdn.com/images/1vf1p12000nscipj6D108.webp
TripLink VISA Card `section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__bg > picture > img.wow`	dimg04.tripcdn.com/images/1vf3w12000qf0e93q41B5.webp
TripLink MasterCard Card `section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__bg > picture > img.wow`	dimg04.tripcdn.com/images/1vf5l12000ndkwlpa6E36.webp
TripLink Partners `section.tl-home-bannerv2__wrap > div.tl-home-bannerv2__content > picture > img.wow`	dimg04.tripcdn.com/images/1vf1p12000n6i148e3A8E.webp
TripLink light logo `section.tl-footer__floor > div.tl-footer__item > picture > img.tl-footer__logo`	dimg04.tripcdn.com/images/1vf0o12000djyrrtw8FA1.webp
Employee Expense `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf2712000n6i15ykF27E.webp
Travel `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf1e12000n6i1cuy6A64.webp
Study Abroad `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf1n12000n6i0w9pBE45.webp
Amazon Ads `div.tl-card-type__content > div.wow > picture > img.tl-card-type__card__img`	dimg04.tripcdn.com/images/1vf4e12000n6i0p4bD6DE.webp
by Trip.com `div.tl-header__wrapper > div.tl-header__content > a.tl-header__logo-wrapper > img.tl-header__logo-suffix`	dimg04.tripcdn.com/images/1vf5h12000n85slnuD8D7.svg
LinkedIn `ul > li.tl-footer__desc-content > a.tl-footer__desc-icon > img`	dimg04.tripcdn.com/images/1vf5z12000ndi3qrjCA45.svg

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 815 KiB

●User Timing marks and measures 4 user timings

●JavaScript execution time 0.1 s

●Minimizes main-thread work 0.5 s

●Network Requests

●Network Round Trip Times 280 ms

●Server Backend Latencies 360 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

ARIA

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cookie-banner-container > section.cookie-banner-words > div.cookie-banner-title > span.cookie-banner-expand `div.cookie-banner-container > section.cookie-banner-words > div.cookie-banner-title > span.cookie-banner-expand`

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.

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
Home `div.tl-nav__wrapper > ul.tl-nav__content > li.tl-nav__item > a.tl-nav__item-content`
Sign In `div.tl-header__wrapper > div.tl-header__content > div.tl-header__right > a.tl-login-btn`
Global `div.Dropdown-control > div.Dropdown-placeholder > div.siteAndLocale_item__R4JHA > span.siteAndLocale_text___w2yb`
English `div.Dropdown-control > div.Dropdown-placeholder > div.siteAndLocale_item__R4JHA > span.siteAndLocale_text___w2yb`
Links `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
Home `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Products `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Solutions `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
About Us `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
About Us `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Our Honour `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Privacy Policy `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Developers `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
API `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
SDK `div.tl-footer__item > ul > li.tl-footer__desc-content > a`
Contact us `div.floor-hash__wrapper > section.tl-footer__floor > div.tl-footer__item > h2.tl-footer__desc-title`
E-mail: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
contact@triplinkintl.com `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Questions Feedback: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
triplinkceo@triplinkintl.com `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Shanghai: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
+86-21-34064880 `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
Hong Kong: `div.tl-footer__item > ul > li.tl-footer__desc-content > span`
+852 58075570 `div.tl-footer__item > ul > li.tl-footer__desc-content > span`

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

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

○Identical links have the same purpose.

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 browser errors logged to the console

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

100

SEO

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://triplinkintl.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 (2)

Usability (1)

Content (1)

Navigation (1)

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

ARIA

Contrast

Best practices

Best Practices

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Best practices

Best Practices

SEO

Keyboard Shortcuts