Elisabeth.berlin Site Title

Kultur Büro Elisabeth Berlin |

Elisabeth.berlin Test Results

Elisabeth.berlin Mobile Performance: 53/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Enable text compression
Potential savings of 296 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Efficiently encode images
Potential savings of 153 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve images in next-gen formats
Potential savings of 310 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.
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.
Largest Contentful Paint element
5,730 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid large layout shifts
15 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Properly size images
Potential savings of 161 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Minify CSS
Potential savings of 34 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce unused CSS
Potential savings of 59 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.
Eliminate render-blocking resources
Potential savings of 1,380 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.
Minify JavaScript
Potential savings of 37 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused JavaScript
Potential savings of 31 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 initial server response time
Root document took 600 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Serve static assets with an efficient cache policy
71 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
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
First Meaningful Paint
3.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
3.4 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.

Elisabeth.berlin Mobile SEO: 85/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
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.

Elisabeth.berlin Mobile Best Practices: 76/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
General
Browser errors were logged to the console
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
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.
Elisabeth.berlin Mobile Accessibility: 83/100
Quick overview:
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.
Skip links are not focusable.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
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.
Similar tests
www.elisabeth.com
www.elisabeth.net
www.elisabeth.org
www.elisabeth.info
www.elisabeth.biz
www.elisabeth.us
www.elisabeth.mobi
www.lisabeth.berlin
www.elisabeth.berlin
www.wlisabeth.berlin
www.ewlisabeth.berlin
www.welisabeth.berlin
www.slisabeth.berlin
www.eslisabeth.berlin
www.selisabeth.berlin
www.dlisabeth.berlin
www.edlisabeth.berlin
www.delisabeth.berlin
www.rlisabeth.berlin
www.erlisabeth.berlin
www.relisabeth.berlin
www.eisabeth.berlin
www.episabeth.berlin
www.elpisabeth.berlin
www.eplisabeth.berlin
www.eoisabeth.berlin
www.eloisabeth.berlin
www.eolisabeth.berlin
www.ekisabeth.berlin
www.elkisabeth.berlin
www.eklisabeth.berlin
www.elsabeth.berlin
www.elusabeth.berlin
www.eliusabeth.berlin
www.eluisabeth.berlin
www.eljsabeth.berlin
www.elijsabeth.berlin
www.eljisabeth.berlin
www.elksabeth.berlin
www.eliksabeth.berlin
www.elosabeth.berlin
www.eliosabeth.berlin
www.eliabeth.berlin
www.eliwabeth.berlin
www.eliswabeth.berlin
www.eliwsabeth.berlin
www.elieabeth.berlin
www.eliseabeth.berlin
www.eliesabeth.berlin
www.elidabeth.berlin
www.elisdabeth.berlin
www.elidsabeth.berlin
www.elizabeth.berlin
www.eliszabeth.berlin
www.elizsabeth.berlin
www.elixabeth.berlin
www.elisxabeth.berlin
www.elixsabeth.berlin
www.eliaabeth.berlin
www.elisaabeth.berlin
www.eliasabeth.berlin
www.elisbeth.berlin
www.elisqbeth.berlin
www.elisaqbeth.berlin
www.elisqabeth.berlin
www.eliswbeth.berlin
www.elisawbeth.berlin
www.elissbeth.berlin
www.elisasbeth.berlin
www.elissabeth.berlin
www.eliszbeth.berlin
www.elisazbeth.berlin
www.elisaeth.berlin
www.elisaveth.berlin
www.elisabveth.berlin
www.elisavbeth.berlin
www.elisageth.berlin
www.elisabgeth.berlin
www.elisagbeth.berlin
www.elisaheth.berlin
www.elisabheth.berlin
www.elisahbeth.berlin
www.elisaneth.berlin
www.elisabneth.berlin
www.elisanbeth.berlin
www.elisabth.berlin
www.elisabwth.berlin
www.elisabewth.berlin
www.elisabweth.berlin
www.elisabsth.berlin
www.elisabesth.berlin
www.elisabseth.berlin
www.elisabdth.berlin
www.elisabedth.berlin
www.elisabdeth.berlin
www.elisabrth.berlin
www.elisaberth.berlin
www.elisabreth.berlin
www.elisabeh.berlin
www.elisaberh.berlin
www.elisabetrh.berlin
www.elisabefh.berlin
www.elisabetfh.berlin
www.elisabefth.berlin
www.elisabegh.berlin
www.elisabetgh.berlin
www.elisabegth.berlin
www.elisabeyh.berlin
www.elisabetyh.berlin
www.elisabeyth.berlin
www.elisabet.berlin
www.elisabetb.berlin
www.elisabethb.berlin
www.elisabetbh.berlin
www.elisabetg.berlin
www.elisabethg.berlin
www.elisabety.berlin
www.elisabethy.berlin
www.elisabetu.berlin
www.elisabethu.berlin
www.elisabetuh.berlin
www.elisabetj.berlin
www.elisabethj.berlin
www.elisabetjh.berlin
www.elisabetn.berlin
www.elisabethn.berlin
www.elisabetnh.berlin
Last Tested: