Skip to content
https://myfritz.net

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.

54

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 long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
sso.myfritz.net/static/css/myfritz-bootstrap.css?v=4.6.350.0 ms80.0 KiB
sso.myfritz.net/static/fonts/fontawesome-webfont.woff86400.0 s97.2 KiB
sso.myfritz.net/static/js/jquery.slim.min.js?v=4.6.350.0 ms38.5 KiB
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Reg...86400.0 s86.3 KiB
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Reg...86400.0 s86.3 KiB
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Sem...86400.0 s85.7 KiB
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Bla...86400.0 s81.6 KiB
sso.myfritz.net/static/images/login-background.png86400.0 s73.8 KiB
sso.myfritz.net/static/js/bootstrap.min.js?v=4.6.350.0 ms27.3 KiB
piwik.avm.de/piwik/piwik.js0.0 ms22.3 KiB
sso.myfritz.net/static/js/myffp.min.js?v=4.6.350.0 ms16.0 KiB
sso.myfritz.net/static/js/uap.min.js?v=4.6.350.0 ms12.7 KiB
sso.myfritz.net/static/js/popper.min.js?v=4.6.350.0 ms11.9 KiB
sso.myfritz.net/static/fonts/fds-iconfont/FDS-Iconfont.woff2?fav9gu86400.0 s22.5 KiB
sso.myfritz.net/static/js/announcements-bundle.js?v=4.6.350.0 ms3.7 KiB
sso.myfritz.net/static/js/reporting-bundle.js0.0 ms2.4 KiB
sso.myfritz.net/static/icons/generic/fritz-logo-white.svg86400.0 s2.9 KiB
sso.myfritz.net/static/icons/generic/fritz-logo-red.svg86400.0 s2.9 KiB
sso.myfritz.net/static/images/help.png86400.0 s2.1 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
sso.myfritz.net/static/fonts/fontawesome-webfont.woff75 ms
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Bla...70 ms
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Reg...55 ms
/static/fonts/source-sans-pro/WOFF2/TTF/SourceSansPro-Sem...55 ms
sso.myfritz.net/static/fonts/fds-iconfont/FDS-Iconfont.woff2?fav9gu40 ms

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:34.183 source:map[column:7049 line:1 type:source-location url:https://sso.myfritz.net/static/js/myffp.min.js?v=4.6.35 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:2.234 source:map[column:15244 line:0 type:source-location url:https://sso.myfritz.net/static/js/myffp.min.js?v=4.6.35 urlProvider:network]] map[reflowTime:31.949 source:map[column:14990 line:0 type:source-location url:https://sso.myfritz.net/static/js/myffp.min.js?v=4.6.35 urlProvider:network]]]

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
Login Forgot password or didn't create one yet? div#kc-content-wrapper > div#kc-form > div#kc-form-wrapper > form#kc-form-login
sso.myfritz.net/static/images/login-background.png72.4 KiB20.8 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-FORM
nodeLabel: Login Forgot password or didn't create one yet?
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,4,FORM
selector: div#kc-content-wrapper > div#kc-form > div#kc-form-wrapper > form#kc-form-login
snippet: <form id="kc-form-login" class="form-signin" action="https://sso.myfritz.net/realms/myfritz/login-actions/authenticate?session_…" method="post">

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
value: no origins were preconnected
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.

URLTransfer SizeDuration
sso.myfritz.net/resources/69h14/login/myfritz/js/login-fp.js?v=4.6.672.5 KiB
sso.myfritz.net/static/js/bootstrap.min.js?v=4.6.3527.3 KiB175 ms
sso.myfritz.net/static/js/jquery.slim.min.js?v=4.6.3538.5 KiB175 ms
sso.myfritz.net/static/js/myffp.min.js?v=4.6.3516.0 KiB
sso.myfritz.net/static/js/uap.min.js?v=4.6.3512.7 KiB175 ms
sso.myfritz.net/static/js/popper.min.js?v=4.6.3511.9 KiB
sso.myfritz.net/resources/69h14/login/myfritz/css/styles.css2.0 KiB
sso.myfritz.net/static/js/reporting-bundle.js2.4 KiB
sso.myfritz.net/static/css/myfritz-bootstrap.css?v=4.6.3580.0 KiB526 ms

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 8.0 s
URLTime Spent
myfritz.net/852 ms
www.myfritz.net/devices/7.1 s
/realms/myfritz/protocol/openid-connect/auth?client_id=bo...0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 15.2 KiB
URLTransfer SizeEst Savings
sso.myfritz.net/static/css/myfritz-bootstrap.css?v=4.6.3580.0 KiB15.2 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 540 ms 41.1 KiB
URLTransfer SizeEst Savings
www.myfritz.net/devices/main-7DFT6ACZ.js39.7 KiB23.5 KiB
www.myfritz.net/devices/polyfills-3WIQBMD5.js17.5 KiB10.4 KiB
www.myfritz.net/devices/chunk-2LZ4GHLU.js20.1 KiB7.3 KiB

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.

Estimated savings: 350 ms 75.1 KiB
URLTransfer SizeEst Savings
sso.myfritz.net/static/css/myfritz-bootstrap.css?v=4.6.3578.5 KiB75.1 KiB

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.

Estimated savings: 180 ms 45.0 KiB
URLTransfer SizeEst Savings
www.myfritz.net/devices/assets/extra-app-config.js?v=4.6.12028.9 KiB23.2 KiB
sso.myfritz.net/static/js/jquery.slim.min.js?v=4.6.3537.1 KiB21.8 KiB

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
nav.header > div.container > a.navbar-brand > img nav.header > div.container > a.navbar-brand > img
sso.myfritz.net/static/icons/generic/fritz-logo-white.svg
footer.container > div.row > div.logo > img footer.container > div.row > div.logo > img
sso.myfritz.net/static/icons/generic/fritz-logo-red.svg
Help nav.header > div.container > a.login-help-button > img
sso.myfritz.net/static/images/help.png

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
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 1,799 KiB
●User Timing marks and measures 37 user timings
●Avoid non-composited animations 1 animated element found
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 40 ms
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 40 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
90

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FRITZ! GmbH div.links > ul > li > a
Imprint div.links > ul > li > a
Contact us div.links > ul > li.last-in-line > a
Data Protection div.links > ul > li > a
Terms of Use div.links > ul > li > a
Version: 4.6.67 div.row > div.links > ul > li
English div#kc-locale > div#kc-locale-wrapper > div#kc-locale-dropdown > a#kc-current-locale-link

These are opportunities to improve the legibility of your content.

Names and labels

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
body > nav.header > div.container > a.navbar-brand body > nav.header > div.container > a.navbar-brand

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.login-pf html.login-pf

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links 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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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]`s are contained by their required parent element
○`[role]` values are valid
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
96

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Help nav.header > div.container > a.login-help-button > img
sso.myfritz.net/static/images/help.png24 x 2424 x 2436 x 36

General

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 about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
www.myfritz.net/devices/chunk-VNETIZY5.js
www.myfritz.net/devices/assets/extra-app-config.js?v=4.6.120sso.myfritz.net/static/js/bootstrap.min.js.map
sso.myfritz.net/static/js/popper.min.js?v=4.6.35sso.myfritz.net/static/js/popper.min.js.map
sso.myfritz.net/static/js/popper.min.js?v=4.6.120sso.myfritz.net/static/js/popper.min.js.map
sso.myfritz.net/static/js/bootstrap.min.js?v=4.6.35sso.myfritz.net/static/js/bootstrap.min.js.map
sso.myfritz.net/static/js/bootstrap.min.js?v=4.6.120sso.myfritz.net/static/js/bootstrap.min.js.map
●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
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
50

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.

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
x-robots-tag: noindex, nofollow
https://sso.myfritz.net/robots.txt

To appear in search results, crawlers need access to your app.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
assets.avm.de/avmstart?target=about-myfritz&language=enhere

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

○Structured data is valid
●Document has a `<title>` element
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback