tapcart.com website review

website-files.com costs a phone 1.6 s of main-thread work and 72.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

14 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.7 s faster on a phone.

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

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 703 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (website-files.com, Google Tag Manager and Hotjar and others), adding 74.1 MB and 5.5 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

Hotjar costs a phone 862 ms of main-thread work and 65 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.

Clarity costs a phone 571 ms of main-thread work and 29 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.

Unbounce costs a phone 516 ms of main-thread work and 372 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.

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

20 KiB JavaScript is shipped twice across bundles. 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).

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

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.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 4.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

10 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 80.1 MB in 302 requests on a phone: media 68.4 MB (27), images 4.5 MB (71) and other files 2.7 MB (66). Under 2 MB keeps phones on slow connections fast.

668c7e0d2700eeddfca1502e_globe-1.gif weighs 1.1 MB. On a phone connection a single image that size takes seconds.

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

3 images further down the page (501 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 67058803ac943a5f43f2ed8a_av.png at 997 px wide, shown at 101 px. Resized copies would save about 46 KiB.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

The homepage links to 73 pages on tapcart.com and 25 external pages.

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.

There is no https://www.tapcart.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.

https://www.tapcart.com/product/tapcart-ai, https://www.tapcart.com/product/for-you-feed and https://www.tapcart.com/integrations/triple-whale are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.tapcart.com/datastories/bfcm-2024 has no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

19 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

Loading the homepage contacts 69 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.