3/30/2021

https://www.usedfurniturebuyerdubai.furniture/

? ? ? ? ?

Performance Accessibility Best SEO Progressive

0–49 50–89 90–100

There were issues affecting this run of Lighthouse:

The page did not paint any content. Please ensure you keep the browser window in the foreground during
the load and try again. (NO_FCP)

Performance
Metrics

First Contentful Paint Error! Time to Interactive Error!

Speed Index Error! Total Blocking Time Error!

Largest Contentful Paint Error! Cumulative Layout Shift Error!

Values are estimated and may vary. The performance score is calculated directly from these metrics. See calculator.

Opportunities — These suggestions can help your page load faster. They don't directly affect the Performance score.

Opportunity Estimated Savings

Eliminate render-blocking resources Error!

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

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

1/15
3/30/2021

Defer offscreen images Error!

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn more.

Minify CSS Error!

Minifying CSS files can reduce network payload sizes. Learn more.

Minify JavaScript Error!

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Remove unused CSS Error!

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce
unnecessary bytes consumed by network activity. Learn more.

Remove unused JavaScript Error!

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Efficiently encode images Error!

Optimized images load faster and consume less cellular data. Learn more.

Serve images in next-gen formats Error!

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means
faster downloads and less data consumption. Learn more.

Enable text compression Error!

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more.

Preconnect to required origins Error!

Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.
Learn more.

Initial server response time was short Error!

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Avoid multiple page redirects Error!

Redirects introduce additional delays before the page can be loaded. Learn more.

Preload key requests Error!

Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn
more.

Use HTTP/2 Error!

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.

2/15
3/30/2021

Use video formats for animated content Error!

Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and
PNG/WebP for static images instead of GIF to save network bytes. Learn more

Remove duplicate modules in JavaScript bundles Error!

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

Avoid serving legacy JavaScript to modern browsers Error!

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

Preload Largest Contentful Paint image Error!

Preload the image used by the LCP element in order to improve your LCP time. Learn more.

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

Avoids enormous network payloads — Error!

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Uses efficient cache policy on static assets — Error!

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

Avoids an excessive DOM size — Error!

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Avoid chaining critical requests — Error!

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.

User Timing marks and measures — Error!

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more.

JavaScript execution time — Error!

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more.

Minimizes main-thread work — Error!

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more

3/15
3/30/2021

All text remains visible during webfont loads — Error!

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Keep request counts low and transfer sizes small — Error!

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Minimize third-party usage — Error!

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.

Lazy load third-party resources with facades — Error!

Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.

Largest Contentful Paint element — Error!

This is the largest contentful element painted within the viewport. Learn More

Avoid large layout shifts — Error!

These DOM elements contribute most to the CLS of the page.

Uses passive listeners to improve scrolling performance — Error!

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Avoids document.write() — Error!

For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of
seconds. Learn more.

Avoid long main-thread tasks — Error!

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Avoid non-composited animations — Error!

Animations which are not composited can be janky and increase CLS. Learn more

Image elements have explicit width and height — Error!

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

Accessibility
These checks highlight opportunities to improve the accessibility of your
web app. Only a subset of accessibility issues can be automatically

4/15
3/30/2021

detected so manual testing is also encouraged.

Navigation — These are opportunities to improve keyboard navigation in your application.

[accesskey] values are unique — Error!

Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.

The page contains a heading, skip link, or landmark region — Error!

Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.

[id] attributes on active, focusable elements are unique — Error!

All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.

Heading elements appear in a sequentially-descending order — Error!

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate
and understand when using assistive technologies. Learn more.

No element has a [tabindex] value greater than 0 — Error!

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating
experiences for users who rely on assistive technologies. Learn more.

ARIA — 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.

[aria-*] attributes match their roles — Error!

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn
more.

button, link, and menuitem elements have accessible names — Error!

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

[aria-hidden="true"] is not present on the document <body> — Error!

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`.
Learn more.

[aria-hidden="true"] elements do not contain focusable descendents — Error!

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to
users of assistive technologies like screen readers. Learn more.

ARIA input fields have accessible names — Error!

When an input field 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 more.

ARIA meter elements have accessible names — Error!

5/15
3/30/2021

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

ARIA progressbar elements have accessible names — Error!

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

[role]s have all required [aria-*] attributes — Error!

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.

Elements with an ARIA [role] that require children to contain a specific [role] have all required children. — Error!

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.

[role]s are contained by their required parent element — Error!

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more.

[role] values are valid — Error!

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.

ARIA toggle fields have accessible names — Error!

When a toggle field 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 more.

ARIA tooltip elements have accessible names — Error!

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

ARIA treeitem elements have accessible names — Error!

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

[aria-*] attributes have valid values — Error!

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.

[aria-*] attributes are valid and not misspelled — Error!

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.

ARIA IDs are unique — Error!

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
more.

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.

6/15
3/30/2021

Buttons have an accessible name — Error!

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.

Document has a <title> element — Error!

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more.

No form fields have multiple labels — Error!

Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either
the first, the last, or all of the labels. Learn more.

<frame> or <iframe> elements have a title — Error!

Screen reader users rely on frame titles to describe the contents of frames. Learn more.

Image elements have [alt] attributes — Error!

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

<input type="image"> elements have [alt] text — Error!

When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the
purpose of the button. Learn more.

Form elements have associated labels — Error!

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

Links have a discernible name — Error!

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.

<object> elements have [alt] text — Error!

Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey
meaning to users. Learn more.

Contrast — These are opportunities to improve the legibility of your content.

Background and foreground colors have a sufficient contrast ratio — Error!

Low-contrast text is difficult or impossible for many users to read. Learn more.

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

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

When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
7/15
3/30/2021

Definition list items are wrapped in <dl> elements — Error!

Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can
properly announce them. Learn more.

Lists contain only <li> elements and script supporting elements (<script> and <template>). — Error!

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

List items (<li>) are contained within <ul> or <ol> parent elements — Error!

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

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

Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only
refer to other cells in the same table may improve the experience for screen reader users. Learn more.

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

Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells
may improve the experience for screen reader users. Learn more.

Internationalization and localization — These are opportunities to improve the interpretation of your content by users in
different locales.

<html> element has a [lang] attribute — Error!

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.

<html> element has a valid value for its [lang] attribute — Error!

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.

[lang] attributes have a valid value — Error!

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
more.

Best practices — These items highlight common accessibility best practices.

The document does not use <meta http-equiv="refresh"> — Error!

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may
create a frustrating or confusing experience. Learn more.

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

— Error!

8/15
3/30/2021

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a
web page. Learn more.

Audio and video — These are opportunities to provide alternative content for audio and video. This may improve the
experience for users with hearing or vision impairments.

<video> elements contain a <track> element with [kind="captions"] — Error!

When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.

Additional items to manually check (10) — These items address areas which an automated testing tool cannot cover. Learn
more in our guide on conducting an accessibility review.

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.

Interactive elements indicate their purpose and state

Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn more.

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

If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.

User focus is not accidentally trapped in a region

A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn more.

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn more.

HTML5 landmark elements are used to improve navigation

Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Learn more.

9/15
3/30/2021

Best Practices
Trust and Safety

Uses HTTPS — Error!

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 served over 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 safe — Error!

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities.
Learn more.

Avoids requesting the geolocation permission on page load — Error!

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user
action instead. Learn more.

Avoids requesting the notification permission on page load — Error!

Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to
user gestures instead. Learn more.

User Experience

Allows users to paste into password fields — Error!

Preventing password pasting undermines good security policy. Learn more.

Displays images with correct aspect ratio — Error!

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

Serves images with appropriate resolution — Error!

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn
more.

Fonts with font-display: optional are preloaded — Error!

Preload `optional` fonts so first-time visitors may use them. Learn More

Browser Compatibility

10/15
3/30/2021

Page has the HTML doctype — Error!

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.

Properly defines charset — Error!

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the
Content-Type HTTP response header. Learn more.

General

Avoids unload event listeners — Error!

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

Avoids Application Cache — Error!

Application Cache is deprecated. Learn more.

Avoids deprecated APIs — Error!

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

No browser errors logged to the console — Error!

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more

Page has valid source maps — Error!

Source maps translate minified code to the original source code. This helps developers debug in production. In addition,
Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn
more.

No issues in the Issues panel in Chrome Devtools — Error!

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request
failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more
details on each issue.

Passed audits (2)

Avoids front-end JavaScript libraries with known security vulnerabilities

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more.

11/15
3/30/2021

SEO
These checks ensure that your page is optimized for search engine results
ranking. There are additional factors Lighthouse does not check that may
affect your search ranking. 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.

Has a <meta name="viewport"> tag with width or initial-scale — Error!

Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.

Document uses legible font sizes — Error!

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to
have >60% of page text ≥12px. Learn more.

Tap targets are sized appropriately — Error!

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.

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

Document has a <title> element — Error!

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more.

Document has a meta description — Error!

Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Links have descriptive text — Error!

Descriptive link text helps search engines understand your content. Learn more.

Image elements have [alt] attributes — Error!

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

Document has a valid hreflang — Error!

hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more.

Document has a valid rel=canonical — Error!

12/15
3/30/2021

Canonical links suggest which URL to show in search results. Learn more.

Document avoids plugins — Error!

Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.

Crawling and Indexing — To appear in search results, crawlers need access to your app.

Page has successful HTTP status code — Error!

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.

Links are crawlable — Error!

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

Page isn’t blocked from indexing — Error!

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.

robots.txt is valid — Error!

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or
indexed. Learn more.

Additional items to manually check (1) — Run these additional validators on your site to check additional SEO best
practices.

Structured data is valid

Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.

Progressive Web App

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason

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. With proper service worker and manifest implementations, browsers can proactively
prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.

13/15
3/30/2021

Failure reason

No manifest was fetched

PWA Optimized

Registers a service worker that controls page and start_url — Error!

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.

Redirects HTTP traffic to HTTPS — Error!

If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web
features for all your users. Learn more.

Is not configured for a custom splash screen Failures: No manifest was fetched.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more.

Sets a theme color for the address bar. — Error!

The browser address bar can be themed to match your site. Learn more.

Content is sized correctly for the viewport — Error!

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile
screens. Learn more.

Has a <meta name="viewport"> tag with width or initial-scale — Error!

Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.

Provides a valid apple-touch-icon — Error!

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It
must point to a non-transparent 192px (or 180px) square PNG. Learn More.

Manifest doesn't have a maskable icon No manifest was fetched

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn more.

Additional items to manually check (3) — These checks are required by the baseline PWA Checklist but are not
automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.

Site works cross-browser

To reach the most number of users, sites should work across every major browser. Learn more.

Page transitions don't feel like they block on the network

14/15
3/30/2021

Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of
performance. Learn more.

Each page has a URL

Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media.
Learn more.

Runtime Settings

URL https://www.usedfurniturebuyerdubai.furniture/

Fetch Time Mar 30, 2021, 4:25 PM GMT+5

Device Emulated Moto G4

Network throttling 150 ms TCP RTT, 1,638.4 Kbps throughput (Simulated)

CPU throttling 4x slowdown (Simulated)

Channel devtools

User agent (host) Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/89.0.4389.90 Safari/537.36

CPU/Memory Power 531

Generated by Lighthouse 7.0.0 | File an issue

15/15