Website review, no card needed

tesalate.com logo

tesalate.com website review

Visit site (opens in a new tab)Reviewed 10 November 202632 issues · 82 checks

This review found 32 issues worth fixing on tesalate.com, 7 of them high impact, across 82 checks. The most urgent: 5 text elements with low contrast. 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s1.0 sMay 23Nov 71.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.2 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.1 s
Nov 7, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
127 ms91 msMay 23Nov 795 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026112 ms
May 30, 2026120 ms
Jun 6, 2026123 ms
Jun 13, 2026122 ms
Jun 20, 2026121 ms
Jun 27, 2026120 ms
Jul 4, 2026118 ms
Jul 11, 2026113 ms
Jul 18, 2026111 ms
Jul 25, 2026103 ms
Aug 1, 202696 ms
Aug 8, 202699 ms
Aug 15, 2026103 ms
Aug 22, 2026106 ms
Aug 29, 2026107 ms
Sep 5, 2026107 ms
Sep 12, 2026104 ms
Sep 19, 2026101 ms
Sep 26, 202696 ms
Oct 3, 202697 ms
Oct 10, 202699 ms
Oct 17, 202697 ms
Oct 24, 202696 ms
Oct 31, 202695 ms
Nov 7, 202695 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of tesalate.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tesalate.com at 0.5 s0.5 s
  2. tesalate.com at 1.0 s1.0 s
  3. tesalate.com at 1.5 s1.5 s
  4. tesalate.com at 2.0 s2.0 s
  5. tesalate.com at 2.5 s2.5 s
  6. tesalate.com at 3.0 s3.0 s
  7. tesalate.com at 3.6 s3.6 s
  8. tesalate.com at 4.1 s4.1 s

Speed

5 to fix55
  • Mobile performance score: 55

    55/100

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

  • Improve image delivery

    958 KiB

    18 images could be 958 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    600 ms · 107 KiB

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

  • Render-blocking requests

    350 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • 1,538 HTML elements

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

  • Use efficient cache lifetimes

    250 ms · 9 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 435 KiB and 187 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 603 ms of it running JavaScript. That is comfortably low.

  • Server response: 10 ms

    10 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.0 s

    10.0 s

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

  • Time to Interactive: 10.3 s

    10.3 s

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

  • Cumulative Layout Shift: 0.303

    0.303

    The layout shifts by 0.303 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 4.3 s

    4.3 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    -8%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 584 ms

    584 ms

    Real visitors wait 584 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 18% faster for real visitors

    -18%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 116 ms

    116 ms

    Scripts block the page for only 116 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 155 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 155 requests on a phone: images 1.7 MB (20), other files 700 KiB (73) and scripts 490 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

12 to fixGoogle 8286
  • 5 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 16 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

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

  • Banner landmark should not be contained in another landmark (1 element)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • No structured data

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

  • One H1 headline

    Your <h1> is empty.

  • 40 internal links, 4 external

    The homepage links to 40 pages on tesalate.com and 4 external pages.

6 checks passed
  • Meta description: 122 characters

    Your meta description is 122 characters: “Tesalate is the original sand free beach towel company from Australia. Over 50 designs, FREE SHIPPING and 45,000+ revie…”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “Beach Towels | Best Sand Free Beach Towels | Tesalate”.

  • Canonical URL set

    The canonical URL is https://au.tesalate.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://au.tesalate.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (628 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://au.tesalate.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 4 pages without a meta description

    https://au.tesalate.com/pages/corporate-gifts, https://au.tesalate.com/collections/shop-all, https://au.tesalate.com/collections/beach-blankets and https://au.tesalate.com/pages/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://au.tesalate.com/pages/contact has 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.

  • 8 pages slow to respond

    https://au.tesalate.com/pages/corporate-gifts, https://au.tesalate.com/collections/shop-all, https://au.tesalate.com/collections/beach-blankets, https://au.tesalate.com/pages/shipping, https://au.tesalate.com/pages/contact and https://au.tesalate.com/pages/terms-conditions and 2 others took over 3 s to send their HTML from our server.

  • 12 internal pages checked

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

6 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 10 small tap targets

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

  • 1 JavaScript error while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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 direct contact details

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

  • About 566 words of copy

    The homepage carries about 566 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop Rashies” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, a star rating and “50,000+ Reviews”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 2 of them by other companies (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.

  • 22 other companies contacted

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

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 tesalate.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Triplewhale · Judge Me Reviews

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Company

Headquarters
Dulwich Hill

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on tesalate.com, including 10 speed issues, 2 SEO issues and 2 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