Nexum.com Site Title

Wir sind nexum.

Nexum.com Meta Description

Einer der größten inhabergeführten digitalen Full-Service-Dienstleister:

Nexum.com Test Results

Nexum.com Mobile Performance: 70/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 170 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
3,810 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
1.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 reduce Javascript execution time.
Avoid an excessive DOM size
1,341 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.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minimize main-thread work
3.0 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 JavaScript
Potential savings of 353 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.
Defer offscreen images
Potential savings of 18 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.
Serve static assets with an efficient cache policy
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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 serve modern JavaScript
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
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.
Max Potential First Input Delay
460 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
11.9 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.
Insights
Layout shift culprits
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Third parties
Third party code can significantly impact load performance. Reduce and defer loading of third party code to prioritize your page's content.

Nexum.com Mobile SEO: 91/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

Nexum.com Mobile Best Practices: 62/100
Quick overview:
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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.
Uses third-party cookies
35 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
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.
Nexum.com Mobile Accessibility: 89/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.
`[role]`s do not have all required `[aria-*]` attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.
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.
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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Similar sites
Similar tests
www.nexum.com
www.nexum.net
www.nexum.org
www.nexum.info
www.nexum.biz
www.nexum.us
www.nexum.mobi
www.exum.com
www.nexum.com
www.bexum.com
www.nbexum.com
www.bnexum.com
www.hexum.com
www.nhexum.com
www.hnexum.com
www.jexum.com
www.njexum.com
www.jnexum.com
www.mexum.com
www.nmexum.com
www.mnexum.com
www.nxum.com
www.nwxum.com
www.newxum.com
www.nwexum.com
www.nsxum.com
www.nesxum.com
www.ndxum.com
www.nedxum.com
www.ndexum.com
www.nrxum.com
www.nerxum.com
www.nrexum.com
www.neum.com
www.nezum.com
www.nexzum.com
www.nezxum.com
www.nesum.com
www.nexsum.com
www.nedum.com
www.nexdum.com
www.necum.com
www.nexcum.com
www.necxum.com
www.nexm.com
www.nexym.com
www.nexuym.com
www.nexyum.com
www.nexhm.com
www.nexuhm.com
www.nexhum.com
www.nexjm.com
www.nexujm.com
www.nexjum.com
www.nexim.com
www.nexuim.com
www.nexium.com
www.nexu.com
www.nexun.com
www.nexumn.com
www.nexunm.com
www.nexuj.com
www.nexumj.com
www.nexuk.com
www.nexumk.com
www.nexukm.com
www.nexum.con
Last Tested: