0898dz.com website review

Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.

About 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

yun300.cn costs a phone 304 ms of main-thread work and 780 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

30 files are served with short cache lifetimes, so returning visitors download them again (60 KiB).

About 51 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

A phone's processor spends 3.3 s on main-thread work while loading, 773 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

2 long tasks block the main thread while loading, the longest for 279 ms. During a long task the page ignores taps.

The page has 1,656 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

5 third-party services load with your homepage (yun300.cn, Baidu Analytics and bdstatic.com and others), adding 793 KiB and 335 ms of main-thread time.

14 images could be 156 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The page becomes fully interactive after 8.3 s. Good is under 3.8 s.

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “沙拉汁系列 沙拉酱系列 发酵糠系列 番茄酱系列 韩式风味酱系列 风味酱系列 豆制品系列 调味粉系列 樱桃系列 果酱系列…”. Most of its time is resource load delay (1.9 s).

The first text or image appears after 2.6 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.

3 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image is downloaded at several times the size a phone draws it, for example b9966e32-8ec4-44c3-bf17-997adca60dfe.jpg_{i}xaf.jpg at 1,080 px wide, shown at 350 px. Resized copies would save about 6 KiB.

1 image (102 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (102 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 28.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

<dt> and <dd> elements must be contained by a <dl>: 19 elements on the page fail this check, rated serious by axe-core.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 6 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 32 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 125 pages on 0898dz.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.0898dz.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.0898dz.com/atlas/4, https://www.0898dz.com/atlas/1, https://www.0898dz.com/atlas/5, https://www.0898dz.com/intro/6.html and https://www.0898dz.com/atlas/2 have no <title>, so Google invents the link text in results.

https://www.0898dz.com/atlas/4, https://www.0898dz.com/atlas/1, https://www.0898dz.com/atlas/5, https://www.0898dz.com/intro/6.html and https://www.0898dz.com/atlas/2 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.0898dz.com/news/14, https://www.0898dz.com/news/15, https://www.0898dz.com/news/4 and https://www.0898dz.com/news/5 use the same meta description. A description written for each page earns more clicks.

https://www.0898dz.com/atlas/4, https://www.0898dz.com/atlas/1, https://www.0898dz.com/atlas/5, https://www.0898dz.com/intro/6.html, https://www.0898dz.com/atlas/2 and https://www.0898dz.com/news/1 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.0898dz.com/product/6, https://www.0898dz.com/product/7, https://www.0898dz.com/product/5, https://www.0898dz.com/product/18, https://www.0898dz.com/news/1 and https://www.0898dz.com/news/14 and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.0898dz.com/recipeBaking.html took over 3 s to send its HTML from our server.

We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

10 images failed to load on a phone, for example https://www.0898dz.com/repository/image/c5f08f43-2132-4a40-9b10-308bedce4c65.png.

23 of 60 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 4 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.