Weofcity.com Site Title

上海薇欧装饰设计工程有限公司-销售建筑装潢材料

Weofcity.com Meta Description

优兔(上海)装饰科技有限公司成立于2017年01月06日,注册地位于上海市青浦区朱家角镇酒龙路292号1幢一层M区130室,法定代表人为朱玉龙。经营范围包括许可项目:各类工程建设活动;建设工程设计。(依法须经批准的项目,经相关部门批准后方可开展经营活动,具体经营项目以相关部门批准文件或许可证件为准)一般项目:技术服务、技术开发、技术咨询、技术交流、技术转让、技术推广,图文设计制作,园林绿化工程施工,企业形象策划,广告制作,广告发布(非广播电台、电视台、报刊出版单位),广告设计、代理,社会经济咨询服务,会议及展览服务,工程管理服务,销售建筑装潢材料、环境保护专用设备、电子产品、户外用品、家具、计算机软硬件及辅助设备、建材、光通信设备。(除依法须经批准的项目外,凭营业执照依法自主开展经营活动)

Weofcity.com Test Results

Weofcity.com Mobile Performance: 28/100
Quick overview:
Time to Interactive
55.7 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.
Optimize DOM size
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size.
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.
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its 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.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Improve image delivery
Est savings of 5,672 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Render blocking requests
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.
Use efficient cache lifetimes
Est savings of 7,230 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Font display
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.
Max Potential First Input Delay
270 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.
Legacy JavaScript
Est savings of 82 KiB
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
7.6 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
Enable text compression
Est savings of 49 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 150 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.
Serve images in next-gen formats
Est savings of 4,964 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.
Reduce unused CSS
Est savings of 69 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Reduce the impact of third-party code
Third-party code blocked the main thread for 720 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.
Largest Contentful Paint element
8,480 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Properly size images
Est savings of 4,348 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce JavaScript execution time
3.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 large layout shifts
11 layout shifts 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
Avoid serving legacy JavaScript to modern browsers
Est savings of 96 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
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`.
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
Defer offscreen images
Est savings of 807 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.
Avoid enormous network payloads
Total size was 13,130 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
82 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Minify CSS
Est savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce unused JavaScript
Est savings of 291 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.

Weofcity.com Mobile SEO: 67/100
Quick overview:
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.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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
robots.txt is not valid
1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Weofcity.com Mobile Best Practices: 41/100
Quick overview:
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
74 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
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.
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 about this errors in console diagnostic audit
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Weofcity.com Mobile Accessibility: 48/100
Quick overview:
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Similar tests
www.weofcity.com
www.weofcity.net
www.weofcity.org
www.weofcity.info
www.weofcity.biz
www.weofcity.us
www.weofcity.mobi
www.eofcity.com
www.weofcity.com
www.qeofcity.com
www.wqeofcity.com
www.qweofcity.com
www.aeofcity.com
www.waeofcity.com
www.aweofcity.com
www.seofcity.com
www.wseofcity.com
www.sweofcity.com
www.eeofcity.com
www.weeofcity.com
www.eweofcity.com
www.wofcity.com
www.wwofcity.com
www.wewofcity.com
www.wweofcity.com
www.wsofcity.com
www.wesofcity.com
www.wdofcity.com
www.wedofcity.com
www.wdeofcity.com
www.wrofcity.com
www.werofcity.com
www.wreofcity.com
www.wefcity.com
www.weifcity.com
www.weoifcity.com
www.weiofcity.com
www.wekfcity.com
www.weokfcity.com
www.wekofcity.com
www.welfcity.com
www.weolfcity.com
www.welofcity.com
www.wepfcity.com
www.weopfcity.com
www.wepofcity.com
www.weocity.com
www.weoccity.com
www.weofccity.com
www.weocfcity.com
www.weodcity.com
www.weofdcity.com
www.weodfcity.com
www.weorcity.com
www.weofrcity.com
www.weorfcity.com
www.weotcity.com
www.weoftcity.com
www.weotfcity.com
www.weogcity.com
www.weofgcity.com
www.weogfcity.com
www.weovcity.com
www.weofvcity.com
www.weovfcity.com
www.weofity.com
www.weofxity.com
www.weofcxity.com
www.weofxcity.com
www.weofdity.com
www.weofcdity.com
www.weoffity.com
www.weofcfity.com
www.weoffcity.com
www.weofvity.com
www.weofcvity.com
www.weofcty.com
www.weofcuty.com
www.weofciuty.com
www.weofcuity.com
www.weofcjty.com
www.weofcijty.com
www.weofcjity.com
www.weofckty.com
www.weofcikty.com
www.weofckity.com
www.weofcoty.com
www.weofcioty.com
www.weofcoity.com
www.weofciy.com
www.weofciry.com
www.weofcitry.com
www.weofcirty.com
www.weofcify.com
www.weofcitfy.com
www.weofcifty.com
www.weofcigy.com
www.weofcitgy.com
www.weofcigty.com
www.weofciyy.com
www.weofcityy.com
www.weofciyty.com
www.weofcit.com
www.weofcitt.com
www.weofcityt.com
www.weofcitty.com
www.weofcitg.com
www.weofcityg.com
www.weofcith.com
www.weofcityh.com
www.weofcithy.com
www.weofcitu.com
www.weofcityu.com
www.weofcituy.com
www.weofcity.con
Last Tested: