Linz.city Site Title

Linz Lemmy - Ein Platz für alle die in oder um Linz wohnen oder ein generelles Interesse daran haben

Linz.city Meta Description

Lemmy

Linz.city Test Results

Linz.city Mobile Performance: 60/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 420 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 CSS
Potential savings of 103 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.
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
4.4 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 JavaScript execution time
2.7 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.
Largest Contentful Paint element
2,620 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid an excessive DOM size
2,889 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.
Minify CSS
Potential savings of 15 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 11 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Reduce unused JavaScript
Potential savings of 293 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.
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Max Potential First Input Delay
2,800 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.
Time to Interactive
9.2 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.

Linz.city Mobile SEO: 100/100
Quick overview:

Linz.city 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.
General
Missing source maps for large first-party JavaScript
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.
Linz.city Mobile Accessibility: 93/100
Quick overview:
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
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.
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.
Elements with visible text labels do not have matching accessible names.
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.
Similar tests
www.linz.com
www.linz.net
www.linz.org
www.linz.info
www.linz.biz
www.linz.us
www.linz.mobi
www.inz.city
www.linz.city
www.pinz.city
www.lpinz.city
www.plinz.city
www.oinz.city
www.loinz.city
www.olinz.city
www.kinz.city
www.lkinz.city
www.klinz.city
www.lnz.city
www.lunz.city
www.liunz.city
www.luinz.city
www.ljnz.city
www.lijnz.city
www.ljinz.city
www.lknz.city
www.liknz.city
www.lonz.city
www.lionz.city
www.liz.city
www.libz.city
www.linbz.city
www.libnz.city
www.lihz.city
www.linhz.city
www.lihnz.city
www.lijz.city
www.linjz.city
www.limz.city
www.linmz.city
www.limnz.city
www.lin.city
www.linx.city
www.linzx.city
www.linxz.city
www.lins.city
www.linzs.city
www.linsz.city
www.lina.city
www.linza.city
www.linaz.city
Last Tested: