Skip to content
https://kriesi.at

Lighthouse Desktop

· 0 checks — Desktop 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.

81

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.

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.

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:5.45 source:map[column:2406 line:38 type:source-location url:https://kriesi.at/wp-content/uploads/dynamic_avia/avia-footer-scripts-a245053ca4aed0837aa1266cd959ab29---69b137c5d6ab1.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:64.43 source:map[type:text value:[unattributed]]] map[reflowTime:0.301 source:map[column:726 line:111 type:source-location url:https://kriesi.at/ urlProvider:network]] map[reflowTime:0.689 source:map[column:50335 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.267 source:map[column:50393 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.243 source:map[column:50457 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:2.969 source:map[column:84992 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:7.404 source:map[column:49615 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.594 source:map[column:51395 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.978 source:map[column:49637 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:1.954 source:map[column:2961 line:79 type:source-location url:https://kriesi.at/wp-content/uploads/dynamic_avia/avia-footer-scripts-a245053ca4aed0837aa1266cd959ab29---69b137c5d6ab1.js urlProvider:network]] map[reflowTime:0.653 source:map[column:3136 line:79 type:source-location url:https://kriesi.at/wp-content/uploads/dynamic_avia/avia-footer-scripts-a245053ca4aed0837aa1266cd959ab29---69b137c5d6ab1.js urlProvider:network]] map[reflowTime:0.175 source:map[column:3174 line:79 type:source-location url:https://kriesi.at/wp-content/uploads/dynamic_avia/avia-footer-scripts-a245053ca4aed0837aa1266cd959ab29---69b137c5d6ab1.js urlProvider:network]] map[reflowTime:0.399 source:map[column:83946 line:1 type:source-location url:https://kriesi.at/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.646 source:map[column:8007 line:79 type:source-location url:https://kriesi.at/wp-content/uploads/dynamic_avia/avia-footer-scripts-a245053ca4aed0837aa1266cd959ab29---69b137c5d6ab1.js urlProvider:network]] map[reflowTime:0.226 source:map[column:98 line:136 type:source-location url:https://pagead2.googlesyndication.com/pagead/managed/js/adsense/m202604160101/show_ads_impl_fy2021.js 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
div.grid-entry > article.main_color > div.grid-image > img.wp-image-3900 div.grid-entry > article.main_color > div.grid-image > img.wp-image-3900
kriesi.at/wp-content/uploads/2019/01/modern.png1.0 MiB1017.4 KiB
div.grid-entry > article.main_color > div.grid-image > img.wp-image-3795 div.grid-entry > article.main_color > div.grid-image > img.wp-image-3795
kriesi.at/wp-content/uploads/2019/01/default.jpg213.8 KiB195.6 KiB
div.grid-entry > article.main_color > div.grid-image > img.wp-image-3796 div.grid-entry > article.main_color > div.grid-image > img.wp-image-3796
kriesi.at/wp-content/uploads/2019/01/shop.jpg196.5 KiB179.7 KiB
div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square
/wp-content/uploads/2021/02/523682_3709844593468_17439251...24.6 KiB23.6 KiB
div.avia-image-container > div.avia-image-container-inner > div.avia-image-overlay-wrap > img.wp-image-3781 div.avia-image-container > div.avia-image-container-inner > div.avia-image-overlay-wrap > img.wp-image-3781
kriesi.at/wp-content/uploads/2019/01/kriesi-themes-new.jpg69.3 KiB18.5 KiB
ul.avia-slideshow-inner > li.avia-slideshow-slide > div.avia-slide-wrap > img.wp-image-1628 ul.avia-slideshow-inner > li.avia-slideshow-slide > div.avia-slide-wrap > img.wp-image-1628
kriesi.at/wp-content/uploads/2013/09/big-banner-front.jpg165.1 KiB14.1 KiB
div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square
kriesi.at/wp-content/uploads/2021/02/IMG_4611-2048x1583-80x80.jpg6.5 KiB5.4 KiB
div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square div.avia-testimonial > div.avia-testimonial_inner > div.avia-testimonial-image > img.attachment-square
kriesi.at/wp-content/uploads/2013/09/testimonial-iris-180x180.jpg9.7 KiB4.4 KiB

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.

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

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: 20 ms 77.4 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.

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
div.avia_textblock > div.avia-principles > div.avia-priciple-main-logo > img div.avia_textblock > div.avia-principles > div.avia-priciple-main-logo > img
kriesi.at/wp-content/themes/kriesi/images/logo.png

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

Max Potential First Input Delay 80 ms
Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,602 KiB
User Timing marks and measures 5 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 1.1 s
Avoid long main-thread tasks 2 long tasks found
Avoid non-composited animations 5 animated elements found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 90 ms
Server Backend Latencies 70 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 180 ms
INP breakdown
LCP request discovery
Avoid large layout shifts
95

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
Premium Themes span.logo > a > span.subtext > strong.logo-title
Demos ul#avia-menu > li#menu-item-3790 > a > span.avia-menu-text
Blog ul#avia-menu > li#menu-item-925 > a > span.avia-menu-text
About ul#avia-menu > li#menu-item-928 > a > span.avia-menu-text
Contact ul#avia-menu > li#menu-item-927 > a > span.avia-menu-text
Support ul#avia-menu > li#menu-item-1812 > a > span.avia-menu-text
We build more than just Themes. We build User Experience for both, you and your… div.entry-content-wrapper > section.av_textblock_section > div.avia_textblock > p
6 principles section.av_textblock_section > div.avia_textblock > p > strong
Sometimes its best to let your work speak for you. Here are some of our most po… div.entry-content-wrapper > section.av_textblock_section > div.avia_textblock > p
View all Demos div.entry-content-wrapper > div.avia-button-wrap > a.avia-color-theme-color > span.avia_iconbox_title
OUR NEWSLETTER div.flex_column > div.av-special-heading > h2.av-special-heading-tag > strong
(We keep your Email address private and we do not spam – promised) div.flex_column > div.av-special-heading > div.av_custom_color > p
Fashion Label div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Kapitan the Brand div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Web Designer div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Philippfischer.at div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Owner div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
IrisEhrlich.at div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link
Video Productions div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > span.avia-testimonial-subtitle
Paul Schuch Video div.avia-testimonial_inner > div.avia-testimonial-meta > div.avia-testimonial-meta-mini > a.avia-testimonial-link

These are opportunities to improve the legibility of your content.

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.html_stretched html.html_stretched

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Kriesi.at Premium Themes div.container > div.inner-container > span.logo > a
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]`s are contained by their required parent element
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
Input buttons have discernible text.
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.
`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
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 have a discernible name
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
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[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
ARIA `progressbar` elements have accessible names
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
Buttons have an accessible name
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 type="image">` elements have `[alt]` text
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
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.
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

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Failed to load resource: the server responded with a status of 404 ()
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 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
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
100

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.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback