Website review, no card needed

ubismartparcel.com logo

ubismartparcel.com website review

Visit site (opens in a new tab)Reviewed 22 October 202647 issues · 82 checks

This review found 47 issues worth fixing on ubismartparcel.com, 16 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of ubismartparcel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ubismartparcel.com at 2.1 s2.1 s
  2. ubismartparcel.com at 4.2 s4.2 s
  3. ubismartparcel.com at 6.3 s6.3 s
  4. ubismartparcel.com at 8.4 s8.4 s
  5. ubismartparcel.com at 10.5 s10.5 s
  6. ubismartparcel.com at 12.6 s12.6 s
  7. ubismartparcel.com at 14.7 s14.7 s
  8. ubismartparcel.com at 16.8 s16.8 s

Speed

11 to fix48
  • Use efficient cache lifetimes

    1.9 s · 3.8 MB

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

  • Render-blocking requests

    3.1 s

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

  • Reduce unused CSS

    1.2 s · 330 KiB

    About 330 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 35). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    450 ms · 1.9 MB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (gtimg.com, Tencent and rumt-zh.com and others), adding 3.6 MB and 1.6 s of main-thread time.

  • gtimg.com adds 825 ms

    825 ms

    gtimg.com costs a phone 825 ms of main-thread work and 1.9 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.

  • Tencent adds 756 ms

    756 ms

    Tencent costs a phone 756 ms of main-thread work and 1.7 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.

  • Minify CSS

    450 ms · 52 KiB

    52 KiB could be saved by minifying CSS.

  • 8 long tasks on the main thread

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

  • Main-thread work: 2.7 s

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

  • Improve image delivery

    67 KiB

    1 image could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Document request latency

    37 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 220 ms

    220 ms

    Your server sent the HTML in 220 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix54
  • Speed Index: 24.0 s

    24.0 s

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

  • Time to Interactive: 26.0 s

    26.0 s

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

  • Total Blocking Time: 946 ms

    946 ms

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

  • Largest Contentful Paint: 4.6 s

    4.6 s

    Your 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 image “推广”. Most of its time is element render delay (9.4 s).

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 5 images without width and height

    5 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
  • Cumulative Layout Shift: 0.056

    0.056

    The layout barely moves while loading (CLS 0.056, good is under 0.1).

Images and page weight

2 to fix60
  • Page weight: 4.3 MB in 72 requests

    4.3 MB

    Your homepage downloads 4.3 MB in 72 requests on a phone: scripts 3.0 MB (28), images 690 KiB (14) and stylesheets 300 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.2 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.

  • About 1.2 g of CO₂ per visit

    1.22 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.22 g of CO₂e: 146.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 6079
  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • <html> element must have a lang attribute (1 element)

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

  • 5 images without alt text

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

  • All page content should be contained by landmarks (3 elements)

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

  • 11 text elements with low contrast

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

  • 7 tap targets too small

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

  • No page language

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • No main landmark

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

1 checks passed
  • 18 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 18 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 7563
  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “UBI 利通智能包裹 - 首页”. 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://ubismartparcel.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ubismartparcel.com/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

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

  • 22 internal links, 10 external

    The homepage links to 22 pages on ubismartparcel.com and 10 external pages.

1 checks passed
  • Meta description: 89 characters

    Your meta description is 89 characters: “UBI利通可提供覆盖全球的空运、海运整柜、海运拼柜、散杂货运输、大件运输、项目物流、演艺物流、快递、跨境电商物流、邮政小包、商业专线、海外仓、履约服务、门到门、端到端等物流服务。”.

AI search readiness

1 to fix83
  • 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://ubismartparcel.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

2 to fix93
  • 10 pages share a meta description

    https://ubismartparcel.com/about.html, https://ubismartparcel.com/service.html, https://ubismartparcel.com/service-OverSeas.html, https://ubismartparcel.com/service-RegularOcean.html, https://ubismartparcel.com/service-UBIAirFreightE2E.html and https://ubismartparcel.com/partner.html and 4 others use the same meta description. A description written for each page earns more clicks.

  • 10 pages without an H1

    https://ubismartparcel.com/about.html, https://ubismartparcel.com/service.html, https://ubismartparcel.com/service-OverSeas.html, https://ubismartparcel.com/service-RegularOcean.html, https://ubismartparcel.com/service-UBIAirFreightE2E.html and https://ubismartparcel.com/partner.html and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://ubismartparcel.com/about.html, https://ubismartparcel.com/service.html, https://ubismartparcel.com/service-OverSeas.html, https://ubismartparcel.com/service-RegularOcean.html, https://ubismartparcel.com/service-UBIAirFreightE2E.html and https://ubismartparcel.com/partner.html and 4 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.

  • 5 pages slow to respond

    https://ubismartparcel.com/service.html, https://ubismartparcel.com/service-RegularOcean.html, https://ubismartparcel.com/service-UBIAirFreightE2E.html, https://ubismartparcel.com/partner.html and https://ubismartparcel.com/news.html took over 3 s to send their HTML from our server.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 10 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • 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 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5089
  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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.”).

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 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

6 to fix25
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 10 words

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

Privacy and tracking

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 ubismartparcel.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on ubismartparcel.com, including 17 speed issues, 8 SEO issues and 6 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25