Pwgkw.com Site Title

天津市甘卫销售有限公司 食品销售 五金产品批发 五金产品零售

Pwgkw.com Meta Description

天津市甘卫销售有限公司成立于2001年09月19日，注册地位于红桥区丁字沽三号路津酒集团旁，法定代表人为田顶会。经营范围包括一般项目：食品销售（仅销售预包装食品）；五金产品批发；五金产品零售；化工产品销售（不含许可类化工产品）；建筑材料销售；轻质建筑材料销售；日用百货销售；日用品批发；日用品销售；文具用品零售；文具用品批发；体育用品及器材批发；体育用品及器材零售；办公设备销售；办公用品销售；教学用模型及教具销售；玩具销售；工艺美术品及收藏品零售（象牙及其制品除外）；工艺美术品及收藏品批发（象牙及其制品除外）；工艺美术品及礼仪用品销售（象牙及其制品除外）；货物进出口；总质量4.5吨及以下普通货运车辆道路货物运输（除网络货运和危险货物）。（除依法须经批准的项目外，凭营业执照依法自主开展经营活动）许可项目：烟草制品零售；电子烟零售。（依法须经批准的项目，经相关部门批准后方可开展经营活动，具体经营项目以相关部门批准文件或许可证件为准）天津市甘卫销售有限公司具有6处分支机构。

Pwgkw.com Test Results

Pwgkw.com Mobile Performance: 95/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 650 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.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 27 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.
Reduce unused CSS
Potential savings of 50 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 7 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid an excessive DOM size
826 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Serve images in next-gen formats
Potential savings of 19 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.
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.
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Insights
Third parties
Third party code can significantly impact load performance. Reduce and defer loading of third party code to prioritize your page's content.
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 viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
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.
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Pwgkw.com Mobile SEO: 100/100
Quick overview:

Pwgkw.com Mobile Best Practices: 66/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.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Pwgkw.com Mobile Accessibility: 69/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.
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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.
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.
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.
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.
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.
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.
Similar sites
Similar tests
www.pwgkw.com
www.pwgkw.net
www.pwgkw.org
www.pwgkw.info
www.pwgkw.biz
www.pwgkw.us
www.pwgkw.mobi
www.wgkw.com
www.pwgkw.com
www.owgkw.com
www.powgkw.com
www.opwgkw.com
www.lwgkw.com
www.plwgkw.com
www.lpwgkw.com
www.pgkw.com
www.pqgkw.com
www.pwqgkw.com
www.pqwgkw.com
www.pagkw.com
www.pwagkw.com
www.pawgkw.com
www.psgkw.com
www.pwsgkw.com
www.pswgkw.com
www.pegkw.com
www.pwegkw.com
www.pewgkw.com
www.pwkw.com
www.pwfkw.com
www.pwgfkw.com
www.pwfgkw.com
www.pwvkw.com
www.pwgvkw.com
www.pwvgkw.com
www.pwtkw.com
www.pwgtkw.com
www.pwtgkw.com
www.pwbkw.com
www.pwgbkw.com
www.pwbgkw.com
www.pwykw.com
www.pwgykw.com
www.pwygkw.com
www.pwhkw.com
www.pwghkw.com
www.pwhgkw.com
www.pwgw.com
www.pwgjw.com
www.pwgkjw.com
www.pwgjkw.com
www.pwgiw.com
www.pwgkiw.com
www.pwgikw.com
www.pwgmw.com
www.pwgkmw.com
www.pwgmkw.com
www.pwglw.com
www.pwgklw.com
www.pwglkw.com
www.pwgow.com
www.pwgkow.com
www.pwgokw.com
www.pwgk.com
www.pwgkq.com
www.pwgkwq.com
www.pwgkqw.com
www.pwgka.com
www.pwgkwa.com
www.pwgkaw.com
www.pwgks.com
www.pwgkws.com
www.pwgksw.com
www.pwgke.com
www.pwgkwe.com
www.pwgkew.com
www.pwgkw.con
Last Tested: