Website review, no card needed
168imperialcity.com website review
Visit site (opens in a new tab)Reviewed 1 November 202642 issues · 77 checks
This review found 42 issues worth fixing on 168imperialcity.com, 16 of them high impact, across 77 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
67D- #113,281 of 126,458 reviewed websitesbeats 9%
- #66,622 of 70,479 online storesbeats 4%
- #818 of 923 BigCommerce storesbeats 10%
Closest competitors among BigCommerce stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.5 s
4.0 s
Speed
Use efficient cache lifetimes
2.5 s · 3.4 MB34 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Improve image delivery
1.1 s · 2.9 MB8 images could be 2.9 MB 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.
Render-blocking requests
2.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
2 third-party services on the page
2 third-party services load with your homepage (Google CDN and globle-un.com), adding 3.2 MB and 36 ms of main-thread time.
globle-un.com adds 1 ms
1 msgloble-un.com costs a phone 1 ms of main-thread work and 3.2 MB 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 65 ms. During a long task the page ignores taps.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 66 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.41
0.41The layout shifts by 0.41 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “私人借貸 人生總會遇上低谷,急需現金週轉。但市面上的大型銀行或財務公司的貸款審查制度嚴謹,往往要求借貸者提供繁複的文件…”. Most of its time is resource load delay (2.1 s).
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.6 s
4.6 sThe page becomes fully interactive after 4.6 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
8 images without width and height
8 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.
1 checks passed
Total Blocking Time: 15 ms
15 msScripts block the page for only 15 ms while loading. Good is under 200 ms.
Images and page weight
3 images over 500 KB
3 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
1.9 MB7 images are downloaded at several times the size a phone draws them, for example banner002.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 1.9 MB.
Page weight: 3.5 MB in 39 requests
3.5 MBYour homepage downloads 3.5 MB in 39 requests on a phone: images 3.3 MB (16), scripts 83 KiB (10) and fonts 74 KiB (1). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (3.1 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.
1 image below the first screen load straight away
1 image further down the page (570 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.99 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (2 elements)
<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 2 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
26 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 26 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (12 characters)
Your title is only 12 characters: “168 皇城財務有限公司”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
No XML sitemap
No XML sitemap at https://168imperialcity.com/sitemap.xml, so Google discovers your pages only by following links.
2 links crawlers can't follow
2 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.
13 internal links, 7 external
The homepage links to 13 pages on 168imperialcity.com and 7 external pages.
2 checks passed
One H1 headline
Your main headline reads: “私人借貸”.
robots.txt in place
robots.txt is in place.
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://168imperialcity.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.
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
9 pages without a meta description
https://168imperialcity.com/pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, https://168imperialcity.com/pages/%E5%80%9F%E8%B2%B8%E6%9C%8D%E5%8B%99.html, https://168imperialcity.com/pages/%E7%A7%81%E4%BA%BA%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E5%95%86%E6%A5%AD%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E6%A8%93%E5%AE%87%E7%89%A9%E6%A5%AD%E6%8C%89%E6%8F%AD.html and https://168imperialcity.com/pages/%E4%B8%80%E7%AD%86%E6%B8%85%E7%B5%90%E9%A4%98%E8%BD%89%E6%88%B6.html and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://168imperialcity.com/pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, https://168imperialcity.com/pages/%E5%80%9F%E8%B2%B8%E6%9C%8D%E5%8B%99.html, https://168imperialcity.com/pages/%E7%A7%81%E4%BA%BA%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E5%95%86%E6%A5%AD%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E6%A8%93%E5%AE%87%E7%89%A9%E6%A5%AD%E6%8C%89%E6%8F%AD.html and https://168imperialcity.com/pages/%E4%B8%80%E7%AD%86%E6%B8%85%E7%B5%90%E9%A4%98%E8%BD%89%E6%88%B6.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://168imperialcity.com/pages/%E9%97%9C%E6%96%BC%E6%88%91%E5%80%91.html, https://168imperialcity.com/pages/%E5%80%9F%E8%B2%B8%E6%9C%8D%E5%8B%99.html, https://168imperialcity.com/pages/%E7%A7%81%E4%BA%BA%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E5%95%86%E6%A5%AD%E8%B2%B8%E6%AC%BE.html, https://168imperialcity.com/pages/%E6%A8%93%E5%AE%87%E7%89%A9%E6%A5%AD%E6%8C%89%E6%8F%AD.html and https://168imperialcity.com/pages/%E4%B8%80%E7%AD%86%E6%B8%85%E7%B5%90%E9%A4%98%E8%BD%89%E6%88%B6.html and 3 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.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 9 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'msie')”.
2 checks passed
Tap targets are thumb-sized
9 of 11 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 38 words
The homepage has only about 38 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.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “EC Shop City”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 168imperialcity.com, 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
- E-commerce
- BigCommerce
- Hosting
- CITIC Telecom International CPC Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on 168imperialcity.com, including 13 speed issues, 7 SEO issues and 4 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.