teascom.com website review

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

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

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

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

1 image could be 104 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

3 third-party services load with your homepage (Shopify, Google Fonts and shop.app), adding 179 KiB and 229 ms of main-thread time.

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

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

9 KiB could be saved by minifying JavaScript.

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 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

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

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

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

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

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 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is only 25 characters: “www.teascom.com – TEASCOM”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 7 characters: “TEASCOM”. 70 to 160 characters is enough to sell the click.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 26 pages on teascom.com and 1 external page.

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.

/pages/packaging and /pages/packing all use the title “Packaging – TEASCOM”. Search engines can't tell which page to show for a search, so each competes with the others.

/pages/merry-tea-xmas, /pages/packaging, /pages/oem-2nd-page, /pages/teaware, /pages/memberships and /pages/about-us and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /pages/packing, whose canonical is /pages/packaging. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/pages/loose-tea, /pages/merry-tea-xmas, /pages/packaging, /pages/oem-2nd-page, /pages/teaware and /pages/memberships and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/loose-tea, /pages/merry-tea-xmas, /pages/oem-2nd-page, /pages/teaware and /pages/memberships 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 13 pages linked from your homepage and read each the way a search engine does.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

teascom.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

teascom.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

The homepage has only about 205 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.

teascom.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be teascom.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 6 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.