Dgfn.eu Site Title

Startseite - DGfN

Dgfn.eu Meta Description

Deutsche Gesellschaft für Nephrologie e.V. / Nierengesellschaft

Dgfn.eu Test Results

Dgfn.eu Mobile Performance: 36/100
Quick overview:
Max Potential First Input Delay
630 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.
First Meaningful Paint
3.7 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
4.3 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid large layout shifts
1 layout shift 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
Eliminate render-blocking resources
Potential savings of 1,320 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 JavaScript
Potential savings of 42 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 the impact of third-party code
Third-party code blocked the main thread for 660 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 how to minimize third-party impact.
Reduce unused CSS
Potential savings of 44 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.
Minimize main-thread work
2.1 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
Avoid multiple page redirects
Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
7,900 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Potential savings of 667 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.
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 about `font-display`.
Avoid an excessive DOM size
894 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.
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Defer offscreen images
Potential savings of 5 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.
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.

Dgfn.eu Mobile SEO: 58/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
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

Dgfn.eu Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 insecure requests 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.
Dgfn.eu Mobile Accessibility: 78/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.
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 about input field labels.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
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 about roles and required children elements.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
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.
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 sites
Similar tests
www.dgfn.com
www.dgfn.net
www.dgfn.org
www.dgfn.info
www.dgfn.biz
www.dgfn.us
www.dgfn.mobi
www.gfn.eu
www.dgfn.eu
www.xgfn.eu
www.dxgfn.eu
www.xdgfn.eu
www.sgfn.eu
www.dsgfn.eu
www.sdgfn.eu
www.egfn.eu
www.degfn.eu
www.edgfn.eu
www.rgfn.eu
www.drgfn.eu
www.rdgfn.eu
www.fgfn.eu
www.dfgfn.eu
www.fdgfn.eu
www.cgfn.eu
www.dcgfn.eu
www.cdgfn.eu
www.dfn.eu
www.dffn.eu
www.dgffn.eu
www.dvfn.eu
www.dgvfn.eu
www.dvgfn.eu
www.dtfn.eu
www.dgtfn.eu
www.dtgfn.eu
www.dbfn.eu
www.dgbfn.eu
www.dbgfn.eu
www.dyfn.eu
www.dgyfn.eu
www.dygfn.eu
www.dhfn.eu
www.dghfn.eu
www.dhgfn.eu
www.dgn.eu
www.dgcn.eu
www.dgfcn.eu
www.dgcfn.eu
www.dgdn.eu
www.dgfdn.eu
www.dgdfn.eu
www.dgrn.eu
www.dgfrn.eu
www.dgrfn.eu
www.dgtn.eu
www.dgftn.eu
www.dggn.eu
www.dgfgn.eu
www.dggfn.eu
www.dgvn.eu
www.dgfvn.eu
www.dgf.eu
www.dgfb.eu
www.dgfnb.eu
www.dgfbn.eu
www.dgfh.eu
www.dgfnh.eu
www.dgfhn.eu
www.dgfj.eu
www.dgfnj.eu
www.dgfjn.eu
www.dgfm.eu
www.dgfnm.eu
www.dgfmn.eu
Last Tested: