Scs.community Site Title
Sovereign Cloud Stack
Scs.community Meta Description
Sovereign Cloud Stack combines the best of cloud computing in one unified standard. SCS is built, backed, and operated by an active open-source community worldwide. Together we put users in control of their data by enabling cloud operators through a decentralized and federated cloud stack – leveraging true digital sovereignty to foster trust in clouds.
Scs.community Test Results
Scs.community Mobile Performance: 58/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Est savings of 65 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
9,930 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Enable text compression
Est savings of 379 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Eliminate render-blocking resources
Est savings of 4,190 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
Est savings of 126 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.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
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
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`.
Serve static assets with an efficient cache policy
57 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused CSS
Est savings of 49 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.
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Render blocking requests
Est savings of 6,630 ms
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Improve image delivery
Est savings of 88 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Font display
Est savings of 70 ms
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Use efficient cache lifetimes
Est savings of 2,148 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Time to Interactive
9.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.
Document request latency
Est savings of 35 KiB
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Scs.community Mobile SEO: 100/100
Quick overview:
Scs.community Mobile Best Practices: 83/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 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.
Scs.community Mobile Accessibility: 85/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.
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.
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.
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 how to provide sufficient color contrast.
Similar sites
Similar tests
www.scs.com
www.scs.net
www.scs.org
www.scs.info
www.scs.biz
www.scs.us
www.scs.mobi
www.cs.community
www.scs.community
www.wcs.community
www.swcs.community
www.wscs.community
www.ecs.community
www.secs.community
www.escs.community
www.dcs.community
www.sdcs.community
www.dscs.community
www.zcs.community
www.szcs.community
www.zscs.community
www.xcs.community
www.sxcs.community
www.xscs.community
www.acs.community
www.sacs.community
www.ascs.community
www.ss.community
www.sxs.community
www.scxs.community
www.sds.community
www.scds.community
www.sfs.community
www.scfs.community
www.sfcs.community
www.svs.community
www.scvs.community
www.svcs.community
www.sc.community
www.scw.community
www.scsw.community
www.scws.community
www.sce.community
www.scse.community
www.sces.community
www.scd.community
www.scsd.community
www.scz.community
www.scsz.community
www.sczs.community
www.scx.community
www.scsx.community
www.sca.community
www.scsa.community
www.scas.community
www.scs.net
www.scs.org
www.scs.info
www.scs.biz
www.scs.us
www.scs.mobi
www.cs.community
www.scs.community
www.wcs.community
www.swcs.community
www.wscs.community
www.ecs.community
www.secs.community
www.escs.community
www.dcs.community
www.sdcs.community
www.dscs.community
www.zcs.community
www.szcs.community
www.zscs.community
www.xcs.community
www.sxcs.community
www.xscs.community
www.acs.community
www.sacs.community
www.ascs.community
www.ss.community
www.sxs.community
www.scxs.community
www.sds.community
www.scds.community
www.sfs.community
www.scfs.community
www.sfcs.community
www.svs.community
www.scvs.community
www.svcs.community
www.sc.community
www.scw.community
www.scsw.community
www.scws.community
www.sce.community
www.scse.community
www.sces.community
www.scd.community
www.scsd.community
www.scz.community
www.scsz.community
www.sczs.community
www.scx.community
www.scsx.community
www.sca.community
www.scsa.community
www.scas.community