tofflon.com website review

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

27 files are served with short cache lifetimes, so returning visitors download them again (13.8 MB).

15 images could be 9.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

55 KiB could be saved by minifying JavaScript.

qixinsz.com costs a phone 0 ms of main-thread work and 628 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.

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

3 third-party services load with your homepage (alicdn.com, gtimg.cn and qixinsz.com), adding 630 KiB and 0 ms of main-thread time.

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.

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

4 KiB could be saved by minifying CSS.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “东富龙科技集团股份有限公司”.

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

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

27 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.

7 images weigh 38.9 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example fa7f97c78991a08ed4916ae2860f5135.png at 3,840 px wide, shown at 195 px. Resized copies would save about 36.4 MB.

Your homepage downloads 25.2 MB in 63 requests on a phone: fonts 11.4 MB (1), images 11.2 MB (41) and media 2.2 MB (1). Under 2 MB keeps phones on slow connections fast.

14 images (40.0 MB) are 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.

7 images further down the page (34.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 images have no alt text, which hurts accessibility and image search.

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

ARIA role should be appropriate for the element: 9 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 13 characters: “东富龙科技集团股份有限公司”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 349 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.

No XML sitemap at https://www.tofflon.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at tofflon.com/robots.txt, the first file search crawlers ask for.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

The homepage links to 65 pages on tofflon.com and 5 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 /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.

Your homepage links to /api/contact.html, which answers with an error. Visitors hit a dead end and search engines drop it.

/, /api/about.html, /api/overall, /api/manage.html, /api/mass.html and /api/culture.html and 8 others all use the title “东富龙科技集团股份有限公司”. Search engines can't tell which page to show for a search, so each competes with the others.

/api/about.html, /api/overall, /api/manage.html, /api/mass.html, /api/culture.html and /api/product and 7 others use the same meta description. A description written for each page earns more clicks.

/api/about.html, /api/overall, /api/manage.html, /api/mass.html, /api/culture.html and /api/cases.html and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

/api/about.html, /api/overall, /api/manage.html, /api/mass.html, /api/culture.html and /api/product and 7 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.

/api/manage.html, /api/culture.html, /api/product, /api/cases.html and /api/invest.html took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://webfiles.qixinsz.com/dongfulong/storage/uploads/20230311/602a375431d051946cda37751f0dbab4.png.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 43 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 1 cookie (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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.