sunways-tech.com website review

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

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

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

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

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

Google CDN costs a phone 428 ms of main-thread work and 733 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.

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

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

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

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

3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 907 KiB and 484 ms of main-thread time.

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

Desktop scores 81 but mobile only 55. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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.

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

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

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

Your largest element takes 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Sunways Grid-Tied Inverters”.

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

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

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

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.2 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

The layout shifts by 0.11 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 206 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 4.7 MB in 120 requests on a phone: images 2.8 MB (23), scripts 968 KiB (39) and fonts 428 KiB (10). Under 2 MB keeps phones on slow connections fast.

1 image (182 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 (21 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 1.33 g of CO₂e: 160.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

5 tap targets are too small or too close together to hit reliably with a finger.

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

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 53 pages on sunways-tech.com and 8 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.sunways-tech.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.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.sunways-tech.com/category/project/residential-projects, whose canonical is https://www.sunways-tech.com/category/residential-projects. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.sunways-tech.com/residential-solar-solutions and https://www.sunways-tech.com/utility-pv-solutions have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sunways-tech.com/sunways-solar-inverter, https://www.sunways-tech.com/residential-solar-solutions, https://www.sunways-tech.com/utility-pv-solutions, https://www.sunways-tech.com/sunways-oem-odm-solution, https://www.sunways-tech.com/category/project/residential-projects and https://www.sunways-tech.com/category/project/ci-projects and 6 others took over 3 s to send their HTML from our server.

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

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

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

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

Your longest form asks for 10 fields (6 required). Every extra field lowers completion.

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

The homepage carries about 676 words of visible text.

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