Skdz.ch Site Title

SKDZ Schule für Kunst und Design Zürich - SKDZ Schule für Kunst und Design Zürich

Skdz.ch Test Results

Skdz.ch Mobile Performance: 51/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Potential savings of 5,761 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce JavaScript execution time
1.5 s
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.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
2.6 s
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
Reduce unused CSS
Potential savings of 35 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.
Serve images in next-gen formats
Potential savings of 3,737 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Defer offscreen images
Potential savings of 10 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Efficiently encode images
Potential savings of 1,327 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Largest Contentful Paint element
43,010 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Eliminate render-blocking resources
Potential savings of 100 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused JavaScript
Potential savings of 253 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 770 ms
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 how to minimize third-party impact.
Serve static assets with an efficient cache policy
20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid an excessive DOM size
1,130 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Avoid enormous network payloads
Total size was 9,462 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Time to Interactive
22.3 s
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.
Max Potential First Input Delay
380 ms
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.
First Meaningful Paint
2.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Skdz.ch Mobile SEO: 82/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description. Description text is empty.
Image elements do not have `[alt]` attributes
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.

Skdz.ch Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
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 about HTTPS.
Skdz.ch Mobile Accessibility: 85/100
Quick overview:
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-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
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.
Links do not have a discernible name
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.
Image elements do not have `[alt]` attributes
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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.skdz.com
www.skdz.net
www.skdz.org
www.skdz.info
www.skdz.biz
www.skdz.us
www.skdz.mobi
www.kdz.ch
www.skdz.ch
www.wkdz.ch
www.swkdz.ch
www.wskdz.ch
www.ekdz.ch
www.sekdz.ch
www.eskdz.ch
www.dkdz.ch
www.sdkdz.ch
www.dskdz.ch
www.zkdz.ch
www.szkdz.ch
www.zskdz.ch
www.xkdz.ch
www.sxkdz.ch
www.xskdz.ch
www.akdz.ch
www.sakdz.ch
www.askdz.ch
www.sdz.ch
www.sjdz.ch
www.skjdz.ch
www.sjkdz.ch
www.sidz.ch
www.skidz.ch
www.sikdz.ch
www.smdz.ch
www.skmdz.ch
www.smkdz.ch
www.sldz.ch
www.skldz.ch
www.slkdz.ch
www.sodz.ch
www.skodz.ch
www.sokdz.ch
www.skz.ch
www.skxz.ch
www.skdxz.ch
www.skxdz.ch
www.sksz.ch
www.skdsz.ch
www.sksdz.ch
www.skez.ch
www.skdez.ch
www.skedz.ch
www.skrz.ch
www.skdrz.ch
www.skrdz.ch
www.skfz.ch
www.skdfz.ch
www.skfdz.ch
www.skcz.ch
www.skdcz.ch
www.skcdz.ch
www.skd.ch
www.skdx.ch
www.skdzx.ch
www.skds.ch
www.skdzs.ch
www.skda.ch
www.skdza.ch
www.skdaz.ch
Last Tested: