Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

Request	Cache TTL	Transfer Size
blog.hypercrites.de/css/fonts/MononokiNerdFontMono-Regular.woff2	0.0 ms	977.6 KiB
blog.hypercrites.de/postimg/f0.jpg	0.0 ms	722.1 KiB
blog.hypercrites.de/img/background_light.jpg	0.0 ms	175.4 KiB
blog.hypercrites.de/postimg/knuhp-exilant.jpg	0.0 ms	91.0 KiB
blog.hypercrites.de/css/webfonts/all.min.css	0.0 ms	74.2 KiB
blog.hypercrites.de/css/fonts/SUSE-Bold.woff2	0.0 ms	44.8 KiB
blog.hypercrites.de/css/fonts/ShareTechMono-Regular.woff	0.0 ms	21.0 KiB
blog.hypercrites.de/css/style.css?2026-04-28	0.0 ms	13.7 KiB
blog.hypercrites.de/css/fonts/artemis.woff2	0.0 ms	4.8 KiB
blog.hypercrites.de/img/overlay.png	0.0 ms	2.6 KiB
blog.hypercrites.de/img/hy_watermark_wr.png	0.0 ms	913 B
blog.hypercrites.de/css/fonts/suse.css	0.0 ms	768 B
blog.hypercrites.de/js/parallax.js	0.0 ms	613 B
blog.hypercrites.de/css/fonts/handschrift.css	0.0 ms	431 B
blog.hypercrites.de/css/fonts/ShareTechMono.css	0.0 ms	415 B
blog.hypercrites.de/css/fonts/mononoki.css	0.0 ms	389 B
blog.hypercrites.de/css/fonts/artemis.css	0.0 ms	362 B

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.

URL	Est Savings
blog.hypercrites.de/css/fonts/MononokiNerdFontMono-Regular.woff2	930 ms
blog.hypercrites.de/css/fonts/SUSE-Bold.woff2	710 ms
blog.hypercrites.de/css/fonts/ShareTechMono-Regular.woff	465 ms
blog.hypercrites.de/css/fonts/artemis.woff2	225 ms

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
blog.hypercrites.de/	http/1.1
blog.hypercrites.de/css/style.css?2026-04-28	http/1.1
blog.hypercrites.de/img/hy_watermark_wr.png	http/1.1
blog.hypercrites.de/postimg/knuhp-exilant.jpg	http/1.1
blog.hypercrites.de/postimg/f0.jpg	http/1.1
blog.hypercrites.de/js/parallax.js	http/1.1
blog.hypercrites.de/css/webfonts/all.min.css	http/1.1
blog.hypercrites.de/css/fonts/artemis.css	http/1.1
blog.hypercrites.de/css/fonts/ShareTechMono.css	http/1.1
blog.hypercrites.de/css/fonts/suse.css	http/1.1
blog.hypercrites.de/css/fonts/mononoki.css	http/1.1
blog.hypercrites.de/css/fonts/handschrift.css	http/1.1
blog.hypercrites.de/img/background_light.jpg	http/1.1
blog.hypercrites.de/img/overlay.png	http/1.1
blog.hypercrites.de/css/fonts/artemis.woff2	http/1.1
blog.hypercrites.de/css/fonts/ShareTechMono-Regular.woff	http/1.1
blog.hypercrites.de/css/fonts/MononokiNerdFontMono-Regular.woff2	http/1.1
blog.hypercrites.de/css/fonts/SUSE-Bold.woff2	http/1.1
blog.hypercrites.de/img/favicon.png	http/1.1
blog.hypercrites.de/img/favicon-32.png	http/1.1

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.

URL	Transfer Size	Duration
blog.hypercrites.de/css/webfonts/all.min.css	74.2 KiB	1.2 s
blog.hypercrites.de/css/fonts/handschrift.css	431 B	457 ms
blog.hypercrites.de/css/fonts/mononoki.css	389 B	457 ms
blog.hypercrites.de/css/fonts/suse.css	768 B	457 ms
blog.hypercrites.de/css/fonts/ShareTechMono.css	415 B	457 ms
blog.hypercrites.de/css/fonts/artemis.css	362 B	457 ms
blog.hypercrites.de/css/style.css?2026-04-28	13.7 KiB	157 ms

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

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.

Estimated savings: 310 ms 73.6 KiB

URL	Transfer Size	Est Savings
blog.hypercrites.de/css/webfonts/all.min.css	74.0 KiB	73.6 KiB

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: 10 ms 4.8 KiB

URL	Transfer Size	Est Savings
blog.hypercrites.de/css/style.css?2026-04-28	13.7 KiB	4.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
F0 `div.post-content > center > p > img`	blog.hypercrites.de/postimg/f0.jpg
Knuddels-HP `div.post-content > center > p > img`	blog.hypercrites.de/postimg/knuhp-exilant.jpg
hYpercrites Logo `div#site > aside#sidebar > div.disc > img.logo`	blog.hypercrites.de/img/hy_watermark_wr.png

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

●Time to Interactive 2.4 s

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●Improve image delivery

●LCP breakdown

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 2,138 KiB

●JavaScript execution time 0.0 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 3 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 220 ms

●Server Backend Latencies 10 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 220 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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
Kleine Gadgets `div.post-list > article.post > h2.post-title > a`
14.04.2026, 12:32 `main#content > div.post-list > article.post > div.post-meta`
Weiterlesen `main#content > div.post-list > article.post > a.read-more`
#gadgets `div.post-list > article.post > div.post-tags > a.tag`
#edc `div.post-list > article.post > div.post-tags > a.tag`
#f0 `div.post-list > article.post > div.post-tags > a.tag`
#f20 `div.post-list > article.post > div.post-tags > a.tag`
#echo mini `div.post-list > article.post > div.post-tags > a.tag`
#fotografie `div.post-list > article.post > div.post-tags > a.tag`
#nikon `div.post-list > article.post > div.post-tags > a.tag`
#d3300 `div.post-list > article.post > div.post-tags > a.tag`
#hobbys `div.post-list > article.post > div.post-tags > a.tag`
Das alte Internet `div.post-list > article.post > h2.post-title > a`
Weiterlesen `main#content > div.post-list > article.post > a.read-more`
#internet `div.post-list > article.post > div.post-tags > a.tag`
#nostalgie `div.post-list > article.post > div.post-tags > a.tag`
#web2.0 `div.post-list > article.post > div.post-tags > a.tag`
#homepages `div.post-list > article.post > div.post-tags > a.tag`
#www `div.post-list > article.post > div.post-tags > a.tag`
Mein Flipper Zero `div.post-list > article.post > h2.post-title > a`
Weiterlesen `main#content > div.post-list > article.post > a.read-more`
#flipper `div.post-list > article.post > div.post-tags > a.tag`
#zero `div.post-list > article.post > div.post-tags > a.tag`
#flipperzero `div.post-list > article.post > div.post-tags > a.tag`
#f0 `div.post-list > article.post > div.post-tags > a.tag`
#nerdkram `div.post-list > article.post > div.post-tags > a.tag`
#pentesting `div.post-list > article.post > div.post-tags > a.tag`
#edc `div.post-list > article.post > div.post-tags > a.tag`

These are opportunities to improve the legibility of your content.

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
2 `div#site > main#content > div.pagination > a.page`

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-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

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

●Links have a discernible name

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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

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 destination	Link Text
blog.hypercrites.de/article/kleine-gadgets	Weiterlesen
blog.hypercrites.de/article/das-alte-internet	Weiterlesen
blog.hypercrites.de/article/mein-flipper-zero	Weiterlesen

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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`