Yxb918.com Site Title
毛鸡收购、宰杀加工、德州鑫滨食品有限公司
Yxb918.com Meta Description
德州鑫滨食品有限公司成立于2002年07月15日，注册地位于山东省德州市禹城市国家高新技术产业开发区汉槐街南华昊路西，法定代表人为闫俊芳。经营范围包括毛鸡收购、宰杀、加工、销售；肉制品生产、销售（含网上销售）；预包装食品、散装食品销售；网站建设及维护；网络技术推广服务。（依法须经批准的项目，经相关部门批准后方可开展经营活动）德州鑫滨食品有限公司具有2处分支机构。
Yxb918.com Test Results
Yxb918.com Mobile Performance: 0/100
Quick overview:
Insights
Optimize viewport for mobile
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
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.
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.
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
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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid large layout shifts
5 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
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
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().
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.
Serve static assets with an efficient cache policy
64 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
Reduce unused CSS
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.
Reduce unused JavaScript
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Use video formats for animated content
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 serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to serve modern JavaScript
Minimize third-party usage
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.
Avoid long main-thread tasks
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Eliminate render-blocking resources
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.
Defer offscreen images
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.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Serve images in next-gen formats
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.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Max Potential First Input Delay
120 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
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.
Yxb918.com Mobile SEO: 82/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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
Yxb918.com Mobile Best Practices: 66/100
Quick overview:
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.
Trust and Safety
Does not use HTTPS
32 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.
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.
User Experience
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.
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 must contain a doctype
Yxb918.com Mobile Accessibility: 41/100
Quick overview:
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.
`<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.
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 sites
Similar tests
www.yxb918.com
www.yxb918.net
www.yxb918.org
www.yxb918.info
www.yxb918.biz
www.yxb918.us
www.yxb918.mobi
www.xb918.com
www.yxb918.com
www.txb918.com
www.ytxb918.com
www.tyxb918.com
www.gxb918.com
www.ygxb918.com
www.gyxb918.com
www.hxb918.com
www.yhxb918.com
www.hyxb918.com
www.uxb918.com
www.yuxb918.com
www.uyxb918.com
www.yb918.com
www.yzb918.com
www.yxzb918.com
www.yzxb918.com
www.ysb918.com
www.yxsb918.com
www.ysxb918.com
www.ydb918.com
www.yxdb918.com
www.ydxb918.com
www.ycb918.com
www.yxcb918.com
www.ycxb918.com
www.yx918.com
www.yxv918.com
www.yxbv918.com
www.yxvb918.com
www.yxg918.com
www.yxbg918.com
www.yxgb918.com
www.yxh918.com
www.yxbh918.com
www.yxhb918.com
www.yxn918.com
www.yxbn918.com
www.yxnb918.com
www.yxb18.com
www.yxb98.com
www.yxb91.com
www.yxb918.con
www.yxb918.net
www.yxb918.org
www.yxb918.info
www.yxb918.biz
www.yxb918.us
www.yxb918.mobi
www.xb918.com
www.yxb918.com
www.txb918.com
www.ytxb918.com
www.tyxb918.com
www.gxb918.com
www.ygxb918.com
www.gyxb918.com
www.hxb918.com
www.yhxb918.com
www.hyxb918.com
www.uxb918.com
www.yuxb918.com
www.uyxb918.com
www.yb918.com
www.yzb918.com
www.yxzb918.com
www.yzxb918.com
www.ysb918.com
www.yxsb918.com
www.ysxb918.com
www.ydb918.com
www.yxdb918.com
www.ydxb918.com
www.ycb918.com
www.yxcb918.com
www.ycxb918.com
www.yx918.com
www.yxv918.com
www.yxbv918.com
www.yxvb918.com
www.yxg918.com
www.yxbg918.com
www.yxgb918.com
www.yxh918.com
www.yxbh918.com
www.yxhb918.com
www.yxn918.com
www.yxbn918.com
www.yxnb918.com
www.yxb18.com
www.yxb98.com
www.yxb91.com
www.yxb918.con