href.li: hide your referrer

Overview

Snoop Summary for href.li

This is a free and comprehensive report about href.li. Href.li is hosted in United States on a server with an IP address of 192.0.78.27, where the local currency is USD and English is the local language. Href.li is expected to earn an estimated $4,781 USD per day from advertising revenue. The sale of href.li would possibly be worth $3,490,188 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Href.li receives an estimated 513,493 unique visitors every day - an insane amount of traffic! This report was last updated 19th June, 2023.

About href.li

Site Preview:
Title:	href.li: hide your referrer
Description:	Make a short link with an expiry date.
Keywords and Tags:	href li bookmarklet, http a href, internet services, li href, phishing, spam
Related Terms:	a href code, hide, hide ip, hide me, hide my ip, hide redirect, href, href open in new tab
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:

Review

Snoop Score

4/5 (Excellent!)

Valuation

$3,490,188 USD

Note: All valuation figures are estimates.

Popularity

Very High

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	4,188
Alexa Reach:	0.0202%
SEMrush Rank (US):	13,297,118
SEMrush Authority Score:	72
Moz Domain Authority:	49
Moz Page Authority:	53

Rank By Country

Country	Alexa Rank
Argentina	3,509
Australia	15,143
Bangladesh	4,925
Czech Republic	881
Egypt	5,322
Ethiopia	1,161
France	744
United Kingdom	2,388
Indonesia	1,618
India	6,900
Iran, Islamic Republic Of	888
Mexico	12,996
Nigeria	8,623
Pakistan	2,669
Poland	750
Russian Federation	3,896
Saudi Arabia	3,744
Thailand	6,667
Turkey	13,201
United States	11,988
Venezuela	4,405
South Africa	6,632

Show Rank By Country

Organic vs Paid (Google Ads)

	Organic	Paid
Keywords:	3	0
Traffic:	3	0
Cost:	$0 USD	$0 USD

Traffic

Visitors

Daily Visitors:	513,493
Monthly Visitors:	15,629,105
Yearly Visitors:	187,424,898

Note: All visitors figures are estimates.

Visitors By Country

Country	Visitors (Unique)	Percentage
Argentina	Daily: 9,756 Monthly: 296,953 Yearly: 3,561,073	1.9%
Australia	Daily: 3,081 Monthly: 93,775 Yearly: 1,124,549	0.6%
Bangladesh	Daily: 3,081 Monthly: 93,775 Yearly: 1,124,549	0.6%
Czech Republic	Daily: 9,756 Monthly: 296,953 Yearly: 3,561,073	1.9%
Egypt	Daily: 6,675 Monthly: 203,178 Yearly: 2,436,524	1.3%
Ethiopia	Daily: 3,081 Monthly: 93,775 Yearly: 1,124,549	0.6%
France	Daily: 77,537 Monthly: 2,359,995 Yearly: 28,301,160	15.1%
United Kingdom	Daily: 16,945 Monthly: 515,760 Yearly: 6,185,022	3.3%
Indonesia	Daily: 18,486 Monthly: 562,648 Yearly: 6,747,296	3.6%
India	Daily: 41,593 Monthly: 1,265,958 Yearly: 15,181,417	8.1%
Iran, Islamic Republic Of	Daily: 41,079 Monthly: 1,250,328 Yearly: 14,993,992	8%
Mexico	Daily: 4,108 Monthly: 125,033 Yearly: 1,499,399	0.8%
Nigeria	Daily: 3,081 Monthly: 93,775 Yearly: 1,124,549	0.6%
Other	Daily: 152,507 Monthly: 4,641,844 Yearly: 55,665,195	29.7%
Pakistan	Daily: 11,810 Monthly: 359,469 Yearly: 4,310,773	2.3%
Poland	Daily: 29,269 Monthly: 890,859 Yearly: 10,683,219	5.7%
Russian Federation	Daily: 17,459 Monthly: 531,390 Yearly: 6,372,447	3.4%
Saudi Arabia	Daily: 7,189 Monthly: 218,807 Yearly: 2,623,949	1.4%
Thailand	Daily: 2,567 Monthly: 78,146 Yearly: 937,124	0.5%
Turkey	Daily: 3,594 Monthly: 109,404 Yearly: 1,311,974	0.7%
United States	Daily: 43,647 Monthly: 1,328,474 Yearly: 15,931,116	8.5%
Venezuela	Daily: 4,108 Monthly: 125,033 Yearly: 1,499,399	0.8%
South Africa	Daily: 3,081 Monthly: 93,775 Yearly: 1,124,549	0.6%

Note: All visitors figures are estimates.

Revenue

Daily Revenue:	$4,781 USD
Monthly Revenue:	$145,521 USD
Yearly Revenue:	$1,745,089 USD

Note: All revenue figures are estimates.

Revenue By Country

Country	Revenue	Percentage
Argentina	Daily: $3 USD Monthly: $101 USD Yearly: $1,207 USD	0.1%
Australia	Daily: $14 USD Monthly: $422 USD Yearly: $5,065 USD	0.3%
Bangladesh	Daily: $2 USD Monthly: $61 USD Yearly: $733 USD	<0.1%
Czech Republic	Daily: $2 USD Monthly: $69 USD Yearly: $830 USD	<0.1%
Egypt	Daily: $2 USD Monthly: $60 USD Yearly: $722 USD	<0.1%
Ethiopia	Daily: $1 USD Monthly: $16 USD Yearly: $194 USD	<0.1%
France	Daily: $424 USD Monthly: $12,920 USD Yearly: $154,933 USD	8.9%
United Kingdom	Daily: $208 USD Monthly: $6,325 USD Yearly: $75,855 USD	4.3%
Indonesia	Daily: $48 USD Monthly: $1,453 USD Yearly: $17,419 USD	1%
India	Daily: $459 USD Monthly: $13,956 USD Yearly: $167,363 USD	9.6%
Iran, Islamic Republic Of	Daily: $0 USD Monthly: $0 USD Yearly: $0 USD	<0.1%
Mexico	Daily: $4 USD Monthly: $122 USD Yearly: $1,460 USD	0.1%
Nigeria	Daily: $3 USD Monthly: $88 USD Yearly: $1,059 USD	0.1%
Other	Daily: $0 USD Monthly: $0 USD Yearly: $0 USD	<0.1%
Pakistan	Daily: $18 USD Monthly: $552 USD Yearly: $6,616 USD	0.4%
Poland	Daily: $24 USD Monthly: $724 USD Yearly: $8,686 USD	0.5%
Russian Federation	Daily: $12 USD Monthly: $359 USD Yearly: $4,310 USD	0.2%
Saudi Arabia	Daily: $6 USD Monthly: $186 USD Yearly: $2,234 USD	0.1%
Thailand	Daily: $2 USD Monthly: $68 USD Yearly: $811 USD	<0.1%
Turkey	Daily: $5 USD Monthly: $148 USD Yearly: $1,769 USD	0.1%
United States	Daily: $3,535 USD Monthly: $107,601 USD Yearly: $1,290,360 USD	73.9%
Venezuela	Daily: $0 USD Monthly: $13 USD Yearly: $162 USD	<0.1%
South Africa	Daily: $9 USD Monthly: $275 USD Yearly: $3,302 USD	0.2%

Note: All revenue figures are estimates.

SEO

Backlinks Analysis (SEMrush)

Backlinks:	19,686,407
Referring Domains:	14,316
Referring IPs:	12,452

Href.li has 19,686,407 backlinks according to SEMrush. 49% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve href.li's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.

99% of href.li's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top Ranking Keywords (US)

1

Keyword: href li bookmarklet

Ranked Page: https://href.li/

2

Keyword: li href

Ranked Page: https://href.li/

3

Keyword: http a href

Ranked Page: https://href.li/

Domain Analysis

	Value	Length
Domain:	href.li	7
Domain Name:	href	4
Extension (TLD):	li	2

Page Speed Analysis

Average Load Time:	0.50 seconds
Load Time Comparison:	Faster than 95% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for href.li. This includes details about optimizing page load times which can result in a better user experience.

Passing (56)

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.

Speed Index — 0.4 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 0.4 s
The timing of the largest text or image that is painted.

Time to Interactive — 0.4 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 0.4 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive href.li as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://href.li/	http/1.1	0	23.460000054911	247	0	301	text/html
https://href.li/	h2	24.19100003317	61.427999986336	1121	1808	200	text/html	Document
https://href.li/href.css?v=3	h2	84.001000039279	99.553999956697	967	1662	200	text/css	Stylesheet

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
106.527	13.656
142.209	6.459
148.684	21.953

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Href.li should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.

Properly size images
Images can slow down the page's load time. Href.li should consider serving more appropriate-sized images.

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Href.li should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Href.li should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Href.li should consider minifying JS files.

Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Href.li should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.

Remove unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.

Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.

Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

Initial server response time was short — Root document took 40 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.

URL	Time Spent (Ms)
https://href.li/	38.227

Show Details

Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Href.li should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://href.li/	190
https://href.li/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Href.li should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.

Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.

Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 2 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://href.li/	1121
https://href.li/href.css?v=3	967
http://href.li/	247

Show Details

Uses efficient cache policy on static assets — 0 resources found
Href.li can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.

Avoids an excessive DOM size — 12 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.

Statistic	Element	Value
Total DOM Elements		12
Maximum DOM Depth	hide the HTTP Referer	4
Maximum Child Elements	Hide the referrer to your URL:	5

Show Details

Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Href.li should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.

JavaScript execution time
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.

Category	Time Spent (Ms)
Style & Layout	24.416
Other	15.457
Script Evaluation	5.355
Parse HTML & CSS	2.379
Rendering	1.786
Script Parsing & Compilation	1.624

Show Details

All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.

Keep request counts low and transfer sizes small — 3 requests • 2 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.

Resource Type	Requests	Transfer Size (Bytes)
Total	3	2335
Document	1	1121
Stylesheet	1	967
Other	1	247
Image	0	0
Media	0	0
Font	0	0
Script	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
href.li: hide your referrer

Show Details

Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of href.li. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Href.li may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.

Failing Elements
href.li bookmarklet - drag this link to your browser toolbar.
href.li

Show Details

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.

Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.

Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.

The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.

User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.

Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.

Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.

Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.

Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.

HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that href.li should incorporate. This includes practices such as protecting pages with HTTPS.

Passing (16)
Failing (2)

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.

Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.

Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.

No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.

Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.

Insecure URL	Request Resolution
http://href.li/	Allowed

Show Details

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for href.li. This includes optimizations such as providing meta data.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Mobile Friendly

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of href.li on mobile screens.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Blocking Directive Source
SHOW DETAILS

Show Details

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of href.li. This includes details about web app manifests.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

Failure reason
No manifest was fetched

Show Details

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data

Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of href.li on mobile screens.

Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.

Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.

Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for href.li. This includes details about optimizing page load times which can result in a better user experience.

Passing (56)
Average (1)

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.

Speed Index — 1.3 s
The time taken for the page contents to be visibly populated.

Largest Contentful Paint — 1.3 s
The timing of the largest text or image that is painted.

Time to Interactive — 1.3 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First CPU Idle — 1.3 s
The time taken for the page's main thread to be quiet enough to handle input.

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive href.li as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://href.li/	http/1.1	0	99.902000001748	264	0	301	text/html
https://href.li/	h2	100.61800000403	146.18699999846	1121	1808	200	text/html	Document
https://href.li/href.css?v=3	h2	213.29100000003	300.06200000207	967	1662	200	text/css	Stylesheet

Show Details

Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.

Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.

Tasks
Below is a list of the top-level main thread tasks that executed during page load.

Start Time (Ms)	End Time (Ms)
378.681	9.12
483.568	11.513

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

First Contentful Paint (3G) — 2460 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.