torontowechat.ca website review

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

About 525 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

9 files are served with short cache lifetimes, so returning visitors download them again (243 KiB).

8 third-party services load with your homepage (posthog.com, Google/Doubleclick Ads and lr-ingest.com and others), adding 1.0 MB and 663 ms of main-thread time.

posthog.com costs a phone 396 ms of main-thread work and 270 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.

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

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

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

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

44 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

19 KiB JavaScript is shipped twice across bundles.

About 16 KiB of CSS is downloaded but never applied on this page.

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.

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “多伦多网”.

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

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

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

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

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 2.2 MB in 134 requests on a phone: scripts 1.1 MB (35), other files 685 KiB (75) and images 217 KiB (8). Under 2 MB keeps phones on slow connections fast.

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

100 elements hidden from screen readers can still receive keyboard focus.

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is only 4 characters: “多伦多网”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 49 characters: “多伦多华人微信群 点击发布你的微信群 发布微信群 发布多伦多公众号 给我们建议 打开微信，扫码进群”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 124 pages on torontowechat.ca and 0 external pages.

Your Organization JSON-LD is missing logo, 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://torontowechat.ca/pages/contact-us, https://torontowechat.ca/pages/%E4%B8%8A%E4%BC%A0%E5%BE%AE%E4%BF%A1%E7%BE%A4, https://torontowechat.ca/pages/%E5%8F%91%E5%B8%83%E5%A4%9A%E4%BC%A6%E5%A4%9A%E5%85%AC%E4%BC%97%E5%8F%B7, https://torontowechat.ca/blogs/news, https://torontowechat.ca/products/%E9%95%BF%E6%9C%9F%E6%8B%9B%E8%81%98%E8%B7%A8%E5%A2%83%E7%94%B5%E5%95%86%E5%AE%A2%E6%9C%8D-%E7%9C%9F%E8%AF%9A%E5%90%88%E4%BD%9C%E5%85%B1%E5%8F%91%E5%B1%95 and https://torontowechat.ca/products/%E8%B7%A8%E5%A2%83%E6%97%BA%E5%AD%A3%E8%AF%9A%E6%8B%9B%E8%B7%A8%E5%A2%83%E7%94%B5%E5%95%86%E5%AE%A2%E6%9C%8D and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://torontowechat.ca/pages/%E4%B8%8A%E4%BC%A0%E5%BE%AE%E4%BF%A1%E7%BE%A4, whose canonical is https://torontowechat.ca/pages/%e4%b8%8a%e4%bc%a0%e5%be%ae%e4%bf%a1%e7%be%a4. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://torontowechat.ca/pages/contact-us, https://torontowechat.ca/pages/%E4%B8%8A%E4%BC%A0%E5%BE%AE%E4%BF%A1%E7%BE%A4, https://torontowechat.ca/pages/%E5%8F%91%E5%B8%83%E5%A4%9A%E4%BC%A6%E5%A4%9A%E5%85%AC%E4%BC%97%E5%8F%B7, https://torontowechat.ca/products/%E9%95%BF%E6%9C%9F%E6%8B%9B%E8%81%98%E8%B7%A8%E5%A2%83%E7%94%B5%E5%95%86%E5%AE%A2%E6%9C%8D-%E7%9C%9F%E8%AF%9A%E5%90%88%E4%BD%9C%E5%85%B1%E5%8F%91%E5%B1%95, https://torontowechat.ca/products/%E8%B7%A8%E5%A2%83%E6%97%BA%E5%AD%A3%E8%AF%9A%E6%8B%9B%E8%B7%A8%E5%A2%83%E7%94%B5%E5%95%86%E5%AE%A2%E6%9C%8D and https://torontowechat.ca/products/%E8%81%98%E8%AF%B7%E8%B7%A8%E5%A2%83%E7%94%B5%E5%95%86%E5%90%88%E4%BC%99%E4%BA%BA-7 and 8 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.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

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