Incept.de Site Title

incept

Incept.de Test Results

Incept.de Mobile Performance: 57/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Preload key requests. Potential savings of 1,920 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Enable text compression. Potential savings of 222 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Reduce initial server response time. Root document took 910 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Serve images in next-gen formats. Potential savings of 139 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.
Remove unused CSS. Potential savings of 55 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.
Remove unused JavaScript. Potential savings of 69 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Serve static assets with an efficient cache policy
21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid chaining critical requests
12 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.
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
Keep request counts low and transfer sizes small
23 requests • 918 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Incept.de Mobile SEO: 92/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.

Incept.de Mobile Best Practices: 86/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 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
2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Incept.de Mobile Progressive Web App: 46/100
Quick overview:
PWA Optimized
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.
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, No `<meta name="theme-color">` tag found.
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.
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
Installable
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.
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.
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.
`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.
Incept.de Mobile Accessibility: 58/100
Quick overview:
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.
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 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.
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 more.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
Similar tests
www.incept.com
www.incept.net
www.incept.org
www.incept.info
www.incept.biz
www.incept.us
www.incept.mobi
www.ncept.de
www.incept.de
www.uncept.de
www.iuncept.de
www.uincept.de
www.jncept.de
www.ijncept.de
www.jincept.de
www.kncept.de
www.ikncept.de
www.kincept.de
www.oncept.de
www.ioncept.de
www.oincept.de
www.icept.de
www.ibcept.de
www.inbcept.de
www.ibncept.de
www.ihcept.de
www.inhcept.de
www.ihncept.de
www.ijcept.de
www.injcept.de
www.imcept.de
www.inmcept.de
www.imncept.de
www.inept.de
www.inxept.de
www.incxept.de
www.inxcept.de
www.indept.de
www.incdept.de
www.indcept.de
www.infept.de
www.incfept.de
www.infcept.de
www.invept.de
www.incvept.de
www.invcept.de
www.incpt.de
www.incwpt.de
www.incewpt.de
www.incwept.de
www.incspt.de
www.incespt.de
www.incsept.de
www.incdpt.de
www.incedpt.de
www.incrpt.de
www.incerpt.de
www.incrept.de
www.incet.de
www.inceot.de
www.incepot.de
www.inceopt.de
www.incelt.de
www.inceplt.de
www.incelpt.de
www.incep.de
www.incepr.de
www.inceptr.de
www.inceprt.de
www.incepf.de
www.inceptf.de
www.incepft.de
www.incepg.de
www.inceptg.de
www.incepgt.de
www.incepy.de
www.incepty.de
www.incepyt.de
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.