Dgm.de Site Title
Home: Deutsche Gesellschaft für Materialkunde e.V.
Dgm.de Test Results
Dgm.de Desktop Performance: 41/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 2,370 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.
Serve images in next-gen formats. Potential savings of 2,315 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.
Properly size images. Potential savings of 1,838 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images. Potential savings of 947 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Avoid multiple page redirects. Potential savings of 380 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Efficiently encode images. Potential savings of 317 KiB
Optimized images load faster and consume less cellular data. 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
128 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
2,749 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid enormous network payloads
Total size was 4,744 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small
134 requests • 4,744 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
68 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Dgm.de Desktop SEO: 80/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. Description text is empty.
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.
Dgm.de Desktop Best Practices: 69/100
Quick overview:
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
10 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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 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.
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.
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
Dgm.de Desktop Progressive Web App: 19/100
Quick overview:
PWA Optimized
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 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.
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
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.
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.
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 15.0 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.
Installable
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 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 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.
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.
Dgm.de Desktop Accessibility: 76/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.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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.
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.
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.
Similar sites
Similar tests
www.dgm.com
www.dgm.net
www.dgm.org
www.dgm.info
www.dgm.biz
www.dgm.us
www.dgm.mobi
www.gm.de
www.dgm.de
www.xgm.de
www.dxgm.de
www.xdgm.de
www.sgm.de
www.dsgm.de
www.sdgm.de
www.egm.de
www.degm.de
www.edgm.de
www.rgm.de
www.drgm.de
www.rdgm.de
www.fgm.de
www.dfgm.de
www.fdgm.de
www.cgm.de
www.dcgm.de
www.cdgm.de
www.dm.de
www.dfm.de
www.dgfm.de
www.dvm.de
www.dgvm.de
www.dvgm.de
www.dtm.de
www.dgtm.de
www.dtgm.de
www.dbm.de
www.dgbm.de
www.dbgm.de
www.dym.de
www.dgym.de
www.dygm.de
www.dhm.de
www.dghm.de
www.dhgm.de
www.dg.de
www.dgn.de
www.dgmn.de
www.dgnm.de
www.dgj.de
www.dgmj.de
www.dgjm.de
www.dgk.de
www.dgmk.de
www.dgkm.de
www.dgm.net
www.dgm.org
www.dgm.info
www.dgm.biz
www.dgm.us
www.dgm.mobi
www.gm.de
www.dgm.de
www.xgm.de
www.dxgm.de
www.xdgm.de
www.sgm.de
www.dsgm.de
www.sdgm.de
www.egm.de
www.degm.de
www.edgm.de
www.rgm.de
www.drgm.de
www.rdgm.de
www.fgm.de
www.dfgm.de
www.fdgm.de
www.cgm.de
www.dcgm.de
www.cdgm.de
www.dm.de
www.dfm.de
www.dgfm.de
www.dvm.de
www.dgvm.de
www.dvgm.de
www.dtm.de
www.dgtm.de
www.dtgm.de
www.dbm.de
www.dgbm.de
www.dbgm.de
www.dym.de
www.dgym.de
www.dygm.de
www.dhm.de
www.dghm.de
www.dhgm.de
www.dg.de
www.dgn.de
www.dgmn.de
www.dgnm.de
www.dgj.de
www.dgmj.de
www.dgjm.de
www.dgk.de
www.dgmk.de
www.dgkm.de