Gscd.cn Site Title

国术建筑装饰(北京)有限公司

Gscd.cn Meta Description

国术建筑装饰(北京)有限公司

Gscd.cn Test Results

Gscd.cn 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
Potential savings of 1,953 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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
Efficiently encode images
Potential savings of 880 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Largest Contentful Paint element
6,090 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce initial server response time
Root document took 670 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Minimize main-thread work
2.9 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
Serve images in next-gen formats
Potential savings of 2,690 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.
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
Serve static assets with an efficient cache policy
77 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 1,531 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.
Reduce unused CSS
Potential savings of 15 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.
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid enormous network payloads
Total size was 4,063 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Eliminate render-blocking resources
Potential savings of 0 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.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Max Potential First Input Delay
600 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
6.4 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.

Gscd.cn Mobile SEO: 82/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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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 about the `alt` attribute.

Gscd.cn Mobile Best Practices: 76/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Trust and Safety
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not use HTTPS
79 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.
Gscd.cn Mobile Accessibility: 58/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 toggle fields do not have accessible names
When a toggle 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 toggle fields.
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-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
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.
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 about the viewport meta tag.
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.
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 about the `alt` attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
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 tests
www.gscd.com
www.gscd.net
www.gscd.org
www.gscd.info
www.gscd.biz
www.gscd.us
www.gscd.mobi
www.scd.cn
www.gscd.cn
www.fscd.cn
www.gfscd.cn
www.fgscd.cn
www.vscd.cn
www.gvscd.cn
www.vgscd.cn
www.tscd.cn
www.gtscd.cn
www.tgscd.cn
www.bscd.cn
www.gbscd.cn
www.bgscd.cn
www.yscd.cn
www.gyscd.cn
www.ygscd.cn
www.hscd.cn
www.ghscd.cn
www.hgscd.cn
www.gcd.cn
www.gwcd.cn
www.gswcd.cn
www.gwscd.cn
www.gecd.cn
www.gsecd.cn
www.gescd.cn
www.gdcd.cn
www.gsdcd.cn
www.gdscd.cn
www.gzcd.cn
www.gszcd.cn
www.gzscd.cn
www.gxcd.cn
www.gsxcd.cn
www.gxscd.cn
www.gacd.cn
www.gsacd.cn
www.gascd.cn
www.gsd.cn
www.gsxd.cn
www.gscxd.cn
www.gsdd.cn
www.gscdd.cn
www.gsfd.cn
www.gscfd.cn
www.gsfcd.cn
www.gsvd.cn
www.gscvd.cn
www.gsvcd.cn
www.gsc.cn
www.gscx.cn
www.gscdx.cn
www.gscs.cn
www.gscds.cn
www.gscsd.cn
www.gsce.cn
www.gscde.cn
www.gsced.cn
www.gscr.cn
www.gscdr.cn
www.gscrd.cn
www.gscf.cn
www.gscdf.cn
www.gscc.cn
www.gscdc.cn
www.gsccd.cn
Last Tested: