psuchina.com website review

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

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

11 images could be 492 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.

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

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

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

4 third-party services load with your homepage (Google Tag Manager, jQuery CDN and alicdn.com and others), adding 219 KiB and 113 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

20 KiB could be saved by minifying CSS.

16 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.6 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 5.4 s (Speed Index). Good is under 3.4 s.

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

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

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

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

Your homepage downloads 7.4 MB in 65 requests on a phone: fonts 5.5 MB (7), images 1.2 MB (23) and scripts 435 KiB (20). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example banner.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 659 KiB.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Headings skip levels (h2 → h4 and h3 → h5), 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.

Your title is 75 characters, so Google will cut it off around 60: “PSU China | Risk & Security Consultancy for International Business in China”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 64 pages on psuchina.com and 4 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.

https://www.psuchina.com/about-us/our-story-values, https://www.psuchina.com/about-us/our-experience-across-industries, https://www.psuchina.com/about-us/our-partnerships-affiliations, https://www.psuchina.com/about-us/our-approach, https://www.psuchina.com/about-us/our-team and https://www.psuchina.com/about-us/careers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.psuchina.com/services/investigations took over 3 s to send its HTML from our server.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 10 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 555 words of visible text.

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