Skip to content
https://github.com/007revad/Synology_Docker_Export

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

51

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

Performance issues directly impact user engagement and conversion rates.

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:25.698 source:map[column:12073 line:2 type:source-location url:https://github.githubassets.com/assets/98944-e7414dc2340e0a21.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:16.722 source:map[type:text value:[unattributed]]] map[reflowTime:25.698 source:map[column:2911 line:1 type:source-location url:https://github.githubassets.com/assets/296-cddf2922ea3a416c.js urlProvider:network]] map[reflowTime:24.625 source:map[column:20578 line:15 type:source-location url:https://github.githubassets.com/assets/26533-36c85461b011ffd5.js urlProvider:network]]]

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
value: No additional origins are good candidates for preconnecting

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.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
article.markdown-body > p > a > img article.markdown-body > p > a > img
/007revad/Synology_Docker_Export/main/images/exports.png34.3 KiB29.2 KiB
article.markdown-body > p > a > img article.markdown-body > p > a > img
/007revad/Synology_Docker_Export/main/images/import-2.png27.6 KiB22.3 KiB
article.markdown-body > p > a > img article.markdown-body > p > a > img
/007revad/Synology_Docker_Export/main/images/import-3.png27.4 KiB22.1 KiB
article.markdown-body > p > a > img article.markdown-body > p > a > img
/007revad/Synology_Docker_Export/main/images/import-1.png24.2 KiB19.6 KiB
article.markdown-body > p > a > img article.markdown-body > p > a > img
raw.githubusercontent.com/007revad/Synology_Docker_Export/main/images/v104.png21.0 KiB15.2 KiB
article.markdown-body > p > a > img article.markdown-body > p > a > img
raw.githubusercontent.com/007revad/Synology_Docker_Export/main/images/script.png8.8 KiB6.4 KiB
@007revad ul.SidebarContributors-module__avatarList__lfU_X > li.SidebarContributors-module__avatarListItem__lW2Qr > a.SidebarContributors-module__avatarLink__ZNrTC > img.prc-Avatar-Avatar-0xaUi
avatars.githubusercontent.com/u/39733752?s=64&v=44.8 KiB4.7 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.7 s
Other1.3 s
Style & Layout1.1 s
Rendering156 ms
Parse HTML & CSS132 ms
Garbage Collection16 ms
Script Parsing & Compilation8.6 ms

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
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/import-2.png
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/import-3.png
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/v104.png
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/exports.png
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/import-1.png
article.markdown-body > p > a > img article.markdown-body > p > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/script.png
div.markdown-heading > h1.heading-element > a > img div.markdown-heading > h1.heading-element > a > img
github.com/007revad/Synology_Docker_Export/raw/main/images/icon.png
Badge article.markdown-body > p > a > img
/97a560c44f2093336a3ee0395f6433e304b1cc20a9b8211c2eca745d...
Donate article.markdown-body > p > a > img
/604e3db9c8751116b3f765aad0353ec7ded655bbe8aaacbc38d8c4a6...

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,947 KiB
●User Timing marks and measures 122 user timings
●Avoid long main-thread tasks 16 long tasks found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 90 ms
●Server Backend Latencies 200 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 460 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
88

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.

Navigation

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 about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Description div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > div.markdown-heading > h3.heading-element

These are opportunities to improve keyboard navigation in your application.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.markdown-heading > h1.heading-element > a > img div.markdown-heading > h1.heading-element > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
article.markdown-body > div.markdown-heading > h1.heading-element > a article.markdown-body > div.markdown-heading > h1.heading-element > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a
div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a div.js-snippet-clipboard-copy-unpositioned > article.markdown-body > p > a

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.

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
Terms nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Privacy nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Security nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Status nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Community nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Docs nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Contact nav > ul.list-style-none > li.mx-2 > a.Link--secondary
Manage cookies ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary
Do not share my personal information ul.list-style-none > li.mx-2 > cookie-consent-link > button.Link--secondary

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●ARIA `progressbar` elements have accessible names
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[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
○`[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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○`<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.
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
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.markdown-heading > h1.heading-element > a > img div.markdown-heading > h1.heading-element > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img
article.markdown-body > p > a > img article.markdown-body > p > a > img

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback