moonoverseas.com website review

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

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

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

18 images could be 1,022 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 88 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 203 ms of main-thread work and 317 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.

5 third-party services load with your homepage (Google Tag Manager, cnzz.com and leadscloud.com and others), adding 334 KiB and 213 ms of main-thread time.

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

About 154 KiB of JavaScript is downloaded but never used on this page.

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

10 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 9 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.

4 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 2.1 MB in 94 requests on a phone: images 1.5 MB (53), scripts 405 KiB (17) and other files 140 KiB (16). Under 2 MB keeps phones on slow connections fast.

17 images (1.4 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.

16 images further down the page (1.3 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 0.60 g of CO₂e: 72.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

12 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

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

Your title is 139 characters, so Google will cut it off around 60: “Since 1956, Moon Environment Technology Co., Ltd. has manufactured some of the most advan…”.

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 273 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 favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

Your <h1> is empty.

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

The homepage links to 143 pages on moonoverseas.com and 9 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.moonoverseas.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.moonoverseas.com/Application/food.jsp, https://www.moonoverseas.com/Application/food/Seafood.jsp, https://www.moonoverseas.com/Application/food/Poultry.jsp, https://www.moonoverseas.com/Application/food/Meat.jsp, https://www.moonoverseas.com/Application/food/Prepared-Food.jsp and https://www.moonoverseas.com/Application/food/Dairy.jsp and 2 others all use the title “Customized system stably food industry solutions-MOON-TECH”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.moonoverseas.com/about/intro.htm, https://www.moonoverseas.com/about/history.htm, https://www.moonoverseas.com/about/honor.jsp and https://www.moonoverseas.com/about/news.jsp have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.moonoverseas.com/Application/food.jsp, https://www.moonoverseas.com/Application/food/Seafood.jsp, https://www.moonoverseas.com/Application/food/Poultry.jsp, https://www.moonoverseas.com/Application/food/Meat.jsp, https://www.moonoverseas.com/Application/food/Prepared-Food.jsp and https://www.moonoverseas.com/Application/food/Dairy.jsp and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.moonoverseas.com/about/chairman.htm, https://www.moonoverseas.com/about/intro.htm, https://www.moonoverseas.com/about/history.htm and https://www.moonoverseas.com/about/honor.jsp took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.moonoverseas.com/.

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.moonoverseas.com/resources/favicon.ico' because its MIME type ('image/x-icon')…”.

2 images are served at too low a resolution for sharp phone screens.

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

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 15 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.