Gzpohe.com Site Title

B2B网站系统_b2b批发系统开发_广州朴荷信息科技有限公司

Gzpohe.com Meta Description

广州朴荷信息科技有限公司成立于2016年09月22日，注册地位于广州市天河区景邮路12号1926房(仅限办公用途)，法定代表人为王刚。经营范围包括信息技术咨询服务;软件开发;信息系统集成服务;计算机批发;软件批发;办公设备耗材批发;电子产品批发;商品批发贸易（许可审批类商品除外）;互联网商品销售（许可审批类商品除外）;家用电器批发;电池销售;纺织品、针织品及原料批发;服装批发;纺织品及针织品零售;小饰物、小礼品零售;日用家电设备零售;软件零售;办公设备耗材零售;电子产品零售;互联网商品零售（许可审批类商品除外）;移动电信业务代理服务;预包装食品零售;

Gzpohe.com Test Results

Gzpohe.com Mobile Performance: 44/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 148 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
12,590 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
Est savings of 1,957 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.
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.
Avoid large layout shifts
3 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
Eliminate render-blocking resources
Est 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 CSS
Est savings of 85 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.2 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
Use video formats for animated content
Est savings of 1,207 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
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().
Serve static assets with an efficient cache policy
92 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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`.
Efficiently encode images
Est savings of 47 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce unused JavaScript
Est savings of 28 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.
Minify CSS
Est savings of 14 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Defer offscreen images
Est savings of 27 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.
Avoid serving legacy JavaScript to modern browsers
Est savings of 7 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
Minify JavaScript
Est savings of 21 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
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
Avoid enormous network payloads
Total size was 5,687 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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.
Legacy JavaScript
Est savings of 27 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
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.
Use efficient cache lifetimes
Est savings of 1,897 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Improve image delivery
Est savings of 3,178 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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.
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.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Time to Interactive
14.5 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.

Gzpohe.com Mobile SEO: 92/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.

Gzpohe.com 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.
Gzpohe.com Mobile Accessibility: 60/100
Quick overview:
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.
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 about the `alt` attribute.
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.
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.
`<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.
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.
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.
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.
Similar sites
Similar tests
www.gzpohe.com
www.gzpohe.net
www.gzpohe.org
www.gzpohe.info
www.gzpohe.biz
www.gzpohe.us
www.gzpohe.mobi
www.zpohe.com
www.gzpohe.com
www.fzpohe.com
www.gfzpohe.com
www.fgzpohe.com
www.vzpohe.com
www.gvzpohe.com
www.vgzpohe.com
www.tzpohe.com
www.gtzpohe.com
www.tgzpohe.com
www.bzpohe.com
www.gbzpohe.com
www.bgzpohe.com
www.yzpohe.com
www.gyzpohe.com
www.ygzpohe.com
www.hzpohe.com
www.ghzpohe.com
www.hgzpohe.com
www.gpohe.com
www.gxpohe.com
www.gzxpohe.com
www.gxzpohe.com
www.gspohe.com
www.gzspohe.com
www.gszpohe.com
www.gapohe.com
www.gzapohe.com
www.gazpohe.com
www.gzohe.com
www.gzoohe.com
www.gzpoohe.com
www.gzopohe.com
www.gzlohe.com
www.gzplohe.com
www.gzlpohe.com
www.gzphe.com
www.gzpihe.com
www.gzpoihe.com
www.gzpiohe.com
www.gzpkhe.com
www.gzpokhe.com
www.gzpkohe.com
www.gzplhe.com
www.gzpolhe.com
www.gzpphe.com
www.gzpophe.com
www.gzppohe.com
www.gzpoe.com
www.gzpobe.com
www.gzpohbe.com
www.gzpobhe.com
www.gzpoge.com
www.gzpohge.com
www.gzpoghe.com
www.gzpoye.com
www.gzpohye.com
www.gzpoyhe.com
www.gzpoue.com
www.gzpohue.com
www.gzpouhe.com
www.gzpoje.com
www.gzpohje.com
www.gzpojhe.com
www.gzpone.com
www.gzpohne.com
www.gzponhe.com
www.gzpoh.com
www.gzpohw.com
www.gzpohew.com
www.gzpohwe.com
www.gzpohs.com
www.gzpohes.com
www.gzpohse.com
www.gzpohd.com
www.gzpohed.com
www.gzpohde.com
www.gzpohr.com
www.gzpoher.com
www.gzpohre.com
www.gzpohe.con
Last Tested: