Linktr.ee Site Title

Link in bio tool: Everything you are, in one simple link | Linktree

Linktr.ee Meta Description

Join 25M+ people and link to everything you create, share and sell online. All from the one bio link.

Linktr.ee Test Results

Linktr.ee Mobile Performance: 14/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 355 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 242 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Eliminate render-blocking resources. Potential savings of 310 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Properly size images. Potential savings of 92 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 45 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 450 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Minimize main-thread work
12.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
22 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
7.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid enormous network payloads
Total size was 3,485 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid an excessive DOM size
950 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small
55 requests • 3,485 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Linktr.ee Mobile SEO: 83/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
94% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Linktr.ee Mobile Best Practices: 71/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Linktr.ee Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 15.3 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Linktr.ee Mobile Accessibility: 66/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Buttons do not have an accessible name
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 more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Links do not have a discernible name
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 more.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar tests
www.linktr.com
www.linktr.net
www.linktr.org
www.linktr.info
www.linktr.biz
www.linktr.us
www.linktr.mobi
www.inktr.ee
www.linktr.ee
www.pinktr.ee
www.lpinktr.ee
www.plinktr.ee
www.oinktr.ee
www.loinktr.ee
www.olinktr.ee
www.kinktr.ee
www.lkinktr.ee
www.klinktr.ee
www.lnktr.ee
www.lunktr.ee
www.liunktr.ee
www.luinktr.ee
www.ljnktr.ee
www.lijnktr.ee
www.ljinktr.ee
www.lknktr.ee
www.liknktr.ee
www.lonktr.ee
www.lionktr.ee
www.liktr.ee
www.libktr.ee
www.linbktr.ee
www.libnktr.ee
www.lihktr.ee
www.linhktr.ee
www.lihnktr.ee
www.lijktr.ee
www.linjktr.ee
www.limktr.ee
www.linmktr.ee
www.limnktr.ee
www.lintr.ee
www.linjtr.ee
www.linkjtr.ee
www.linitr.ee
www.linkitr.ee
www.liniktr.ee
www.linmtr.ee
www.linkmtr.ee
www.linltr.ee
www.linkltr.ee
www.linlktr.ee
www.linotr.ee
www.linkotr.ee
www.linoktr.ee
www.linkr.ee
www.linkrr.ee
www.linktrr.ee
www.linkrtr.ee
www.linkfr.ee
www.linktfr.ee
www.linkftr.ee
www.linkgr.ee
www.linktgr.ee
www.linkgtr.ee
www.linkyr.ee
www.linktyr.ee
www.linkytr.ee
www.linkt.ee
www.linkte.ee
www.linktre.ee
www.linkter.ee
www.linktd.ee
www.linktrd.ee
www.linktdr.ee
www.linktf.ee
www.linktrf.ee
www.linktt.ee
www.linktrt.ee
www.linkttr.ee
Last Tested: