akocommerce.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and jotfor.ms and others), adding 2.8 MB and 882 ms of main-thread time.

Google CDN costs a phone 349 ms of main-thread work and 1.0 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.

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

Google Tag Manager costs a phone 179 ms of main-thread work and 307 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.

jotfor.ms costs a phone 104 ms of main-thread work and 919 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.

2 images could be 65 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.

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

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

17 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 44.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

1 image 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 8.5 MB in 341 requests on a phone: fonts 5.0 MB (92), scripts 1.7 MB (73) and other files 1.1 MB (130). Under 2 MB keeps phones on slow connections fast.

pf-a59ef450--banner02.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

Your meta description is 183 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.

Your <h1> is empty.

The homepage links to 47 pages on akocommerce.com and 8 external pages.

https://akocommerce.com/pages/contact-us-booking, https://akocommerce.com/pages/book-shopify and https://akocommerce.com/pages/book-cvs all use the title “Shopify台灣｜Shopify 建站免費諮詢，開始免費試用｜AkoCommerce”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://akocommerce.com/collections/showcase, https://akocommerce.com/pages/our-service, https://akocommerce.com/collections/%E6%A1%88%E4%BE%8B%E5%88%86%E4%BA%AB and https://akocommerce.com/en/collections/%E6%A1%88%E4%BE%8B%E5%88%86%E4%BA%AB have no meta description, so Google writes the search snippet from whatever text it finds.

https://akocommerce.com/pages/contact-us-booking, https://akocommerce.com/pages/book-shopify and https://akocommerce.com/pages/book-cvs use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://akocommerce.com/pages/book-shopify, whose canonical is https://akocommerce.com/pages/contact-us-booking. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://akocommerce.com/pages/contact-us-booking, https://akocommerce.com/collections/showcase, https://akocommerce.com/blogs/shopify-news, https://akocommerce.com/blogs/shopify-tutorials, https://akocommerce.com/blogs/shopify-success-stories and https://akocommerce.com/blogs/shopify 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.

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

9 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

3 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 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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 12 cookies, 1 of them by other companies (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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.