Website review, no card needed
malverncollege.cn website review
Visit site (opens in a new tab)Reviewed 24 October 202641 issues · 79 checks
This review found 41 issues worth fixing on malverncollege.cn, 17 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.7 s
3.5 s
5.2 s
7.0 s
8.7 s
10.5 s
12.2 s
14.0 s
Speed
Use efficient cache lifetimes
5.7 s · 1.5 MB32 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
6.2 s16 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.2 s.
Reduce unused JavaScript
2.5 s · 591 KiBAbout 591 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Reduce unused CSS
1.5 s · 188 KiBAbout 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Improve image delivery
1.1 s · 386 KiB4 images could be 386 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 77). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (53kf.com, Google Tag Manager and Baidu Analytics and others), adding 1.3 MB and 779 ms of main-thread time.
53kf.com adds 546 ms
546 ms53kf.com costs a phone 546 ms of main-thread work and 622 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.
aliyuncs.com adds 0 ms
0 msaliyuncs.com costs a phone 0 ms of main-thread work and 518 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.
Minify JavaScript
83 KiB83 KiB could be saved by minifying JavaScript.
Document request latency
28 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Phones get a much slower page than desktops
Desktop scores 77 but mobile only 31. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 802 ms of it running JavaScript. That is comfortably low.
Server response: 228 ms
228 msYour server sent the HTML in 228 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.8 s
15.8 sVisually, the page fills in at 15.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.426
0.426The layout shifts by 0.426 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 251 ms
251 msScripts block taps and scrolling for 251 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
Images and page weight
Page weight: 2.3 MB in 131 requests
2.3 MBYour homepage downloads 2.3 MB in 131 requests on a phone: scripts 1.0 MB (27), images 982 KiB (76) and stylesheets 237 KiB (14). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (637 KiB) 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.
1 image far larger than shown
20 KiB1 image is downloaded at several times the size a phone draws it, for example index-page-bg-0.jpg at 1,920 px wide, shown at 624 px. Resized copies would save about 20 KiB.
2 images below the first screen load straight away
2 images further down the page (81 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 77.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
43 internal links, 2 external
The homepage links to 43 pages on malverncollege.cn and 2 external pages.
4 checks passed
Meta description: 81 characters
Your meta description is 81 characters: “青岛墨尔文中学是一所国际化民办中学,将英式精英教育的精髓与中国学生特点相结合,制定出一套适合中国学生、有前瞻性的全人领袖培养模式,让学生得到真正的“墨尔文”体验。”.
Title: 35 characters
Your title is a healthy 35 characters: “青岛墨尔文中学MALVERN COLLEGE QINGDAO|官方网站”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://malverncollege.cn/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://malverncollege.cn/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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
8 pages share 4 titles
/ and https://malverncollege.cn/en all use the title “青岛墨尔文中学MALVERN COLLEGE QINGDAO|官方网站”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://malverncollege.cn/calendar, https://malverncollege.cn/about, https://malverncollege.cn/about/p/mcqd, https://malverncollege.cn/about/p/jiaoyuyuanjing, https://malverncollege.cn/about/p/xuexiaolishi and https://malverncollege.cn/about/p/jiaruwomen and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://malverncollege.cn/en, https://malverncollege.cn/calendar, https://malverncollege.cn/about, https://malverncollege.cn/about/p/mcqd, https://malverncollege.cn/about/p/jiaoyuyuanjing and https://malverncollege.cn/about/p/xuexiaolishi and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://malverncollege.cn/calendar, https://malverncollege.cn/about, https://malverncollege.cn/about/p/mcqd, https://malverncollege.cn/about/p/jiaoyuyuanjing, https://malverncollege.cn/about/p/jiaruwomen and https://malverncollege.cn/activity and 6 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.
2 pages slow to respond
https://malverncollege.cn/calendar and https://malverncollege.cn/about/p/mcqd took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://malverncollege.cn/.
2 small tap targets
2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 39 words
The homepage has only about 39 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
No consent tool detected
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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at malverncollege.cn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on malverncollege.cn, including 16 speed issues, 5 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.