Bkh.cat Site Title
Katzen- BKH / BRI Zucht
Bkh.cat Meta Description
Seriöse Katzenzucht für die schönsten
Bkh.cat Test Results
Bkh.cat Mobile Performance: 30/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 2,723 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Defer offscreen images. Potential savings of 3,649 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Remove unused CSS. Potential savings of 869 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 914 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Eliminate render-blocking resources. Potential savings of 4,220 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Properly size images. Potential savings of 563 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused JavaScript. Potential savings of 504 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 206 KiB
Optimized images load faster and consume less cellular data. Learn more.
Reduce initial server response time. Root document took 750 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Minify CSS. Potential savings of 92 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,160 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 more.
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.
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.
Avoid enormous network payloads
Total size was 6,614 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Serve static assets with an efficient cache policy
15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
4.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
2.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Keep request counts low and transfer sizes small
33 requests • 6,614 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
User Timing marks and measures
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid long main-thread tasks
14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Bkh.cat Mobile SEO: 77/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 valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more. Relative URL (Britisch Kurzhaar Katzenzucht)
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.
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 More
Bkh.cat Mobile Best Practices: 71/100
Quick overview:
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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 servedover 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.
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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
Bkh.cat Mobile Progressive Web App: 21/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Fast and reliable
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 20.6 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Installable
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 servedover 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.
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Bkh.cat Mobile Accessibility: 71/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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Similar tests
www.bkh.com
www.bkh.net
www.bkh.org
www.bkh.info
www.bkh.biz
www.bkh.us
www.bkh.mobi
www.kh.cat
www.bkh.cat
www.vkh.cat
www.bvkh.cat
www.vbkh.cat
www.gkh.cat
www.bgkh.cat
www.gbkh.cat
www.hkh.cat
www.bhkh.cat
www.hbkh.cat
www.nkh.cat
www.bnkh.cat
www.nbkh.cat
www.bh.cat
www.bjh.cat
www.bkjh.cat
www.bjkh.cat
www.bih.cat
www.bkih.cat
www.bikh.cat
www.bmh.cat
www.bkmh.cat
www.bmkh.cat
www.blh.cat
www.bklh.cat
www.blkh.cat
www.boh.cat
www.bkoh.cat
www.bokh.cat
www.bk.cat
www.bkb.cat
www.bkhb.cat
www.bkbh.cat
www.bkg.cat
www.bkhg.cat
www.bkgh.cat
www.bky.cat
www.bkhy.cat
www.bkyh.cat
www.bku.cat
www.bkhu.cat
www.bkuh.cat
www.bkj.cat
www.bkhj.cat
www.bkn.cat
www.bkhn.cat
www.bknh.cat
www.bkh.net
www.bkh.org
www.bkh.info
www.bkh.biz
www.bkh.us
www.bkh.mobi
www.kh.cat
www.bkh.cat
www.vkh.cat
www.bvkh.cat
www.vbkh.cat
www.gkh.cat
www.bgkh.cat
www.gbkh.cat
www.hkh.cat
www.bhkh.cat
www.hbkh.cat
www.nkh.cat
www.bnkh.cat
www.nbkh.cat
www.bh.cat
www.bjh.cat
www.bkjh.cat
www.bjkh.cat
www.bih.cat
www.bkih.cat
www.bikh.cat
www.bmh.cat
www.bkmh.cat
www.bmkh.cat
www.blh.cat
www.bklh.cat
www.blkh.cat
www.boh.cat
www.bkoh.cat
www.bokh.cat
www.bk.cat
www.bkb.cat
www.bkhb.cat
www.bkbh.cat
www.bkg.cat
www.bkhg.cat
www.bkgh.cat
www.bky.cat
www.bkhy.cat
www.bkyh.cat
www.bku.cat
www.bkhu.cat
www.bkuh.cat
www.bkj.cat
www.bkhj.cat
www.bkn.cat
www.bkhn.cat
www.bknh.cat