Website review, no card needed

sheret.com logo

sheret.com website review

Visit site (opens in a new tab)Reviewed 31 October 202634 issues · 82 checks

This review found 34 issues worth fixing on sheret.com, 7 of them high impact, across 82 checks. The most urgent: required ARIA attributes must be provided (1 element). 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
978 ms755 msMay 9Oct 24858 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026945 ms
May 16, 2026952 ms
May 23, 2026941 ms
May 30, 2026925 ms
Jun 6, 2026929 ms
Jun 13, 2026926 ms
Jun 20, 2026927 ms
Jun 27, 2026930 ms
Jul 4, 2026907 ms
Jul 11, 2026868 ms
Jul 18, 2026830 ms
Jul 25, 2026791 ms
Aug 1, 2026781 ms
Aug 8, 2026783 ms
Aug 15, 2026782 ms
Aug 22, 2026784 ms
Aug 29, 2026789 ms
Sep 5, 2026799 ms
Sep 12, 2026811 ms
Sep 19, 2026812 ms
Sep 26, 2026827 ms
Oct 3, 2026835 ms
Oct 10, 2026847 ms
Oct 17, 2026861 ms
Oct 24, 2026858 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms75 msMay 9Oct 2479 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202676 ms
May 16, 202677 ms
May 23, 202677 ms
May 30, 202678 ms
Jun 6, 202678 ms
Jun 13, 202678 ms
Jun 20, 202679 ms
Jun 27, 202680 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202678 ms
Aug 1, 202678 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202679 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202679 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 sheret.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sheret.com at 0.4 s0.4 s
  2. sheret.com at 0.8 s0.8 s
  3. sheret.com at 1.1 s1.1 s
  4. sheret.com at 1.5 s1.5 s
  5. sheret.com at 1.9 s1.9 s
  6. sheret.com at 2.3 s2.3 s
  7. sheret.com at 2.6 s2.6 s
  8. sheret.com at 3.0 s3.0 s

Speed

3 to fix95
  • Improve image delivery

    933 KiB

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

  • Render-blocking requests

    750 ms

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

  • Google Tag Manager adds 351 ms

    351 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google/Doubleclick Ads and others), adding 575 KiB and 361 ms of main-thread time.

  • Reduce unused JavaScript

    201 KiB

    About 201 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Reduce unused CSS

    40 KiB

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

  • Legacy JavaScript

    10 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

  • Use efficient cache lifetimes

    4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

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

  • Server response: 62 ms

    62 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 7.7 s

    7.7 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

10 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: 0.9 s

    0.9 s

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

  • Real-user INP: 72 ms

    72 ms

    Real visitors wait 72 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 413 ms

    413 ms

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 108 ms

    108 ms

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

  • Cumulative Layout Shift: 0.044

    0.044

    The layout barely moves while loading (CLS 0.044, good is under 0.1).

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Canada's Leading Distributor of Plumbing & Heating Supplies”.

Images and page weight

2 to fix80
  • 9 images in older formats

    9 images (1.0 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.

  • 1 image far larger than shown

    258 KiB

    1 image is downloaded at several times the size a phone draws it, for example FireProtection-d3f9a6d3d8ecf59292416c91fc2b1871.jpg at 1,296 px wide, shown at 111 px. Resized copies would save about 258 KiB.

  • About 0.5 g of CO₂ per visit

    0.53 g

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

2 checks passed
  • Page weight: 1.9 MB in 46 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 46 requests on a phone: images 1.0 MB (13), scripts 635 KiB (13) and fonts 133 KiB (2). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

8 to fixGoogle 7487
  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 10 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

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

  • 10 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

1 checks passed
  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9263
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Canada's Trusted Source for Plumbing and Heating Supplies Since 1892”.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (203 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.sheret.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 38 internal links, 3 external

    The homepage links to 38 pages on sheret.com and 3 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

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

  • No llms.txt

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

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

Other pages

3 to fix83
  • 2 pages share a title

    https://www.sheret.com/contactus and https://www.sheret.com/contact all use the title “Contact Us - Andrew Sheret Limited”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.sheret.com/promotions, https://www.sheret.com/careers, https://www.sheret.com/contactus, https://www.sheret.com/company, https://www.sheret.com/contact and https://www.sheret.com/policies_and_terms have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.sheret.com/plumbing, https://www.sheret.com/heating, https://www.sheret.com/hvac, https://www.sheret.com/irrigation, https://www.sheret.com/pumps and https://www.sheret.com/waterworks and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://www.sheret.com/contactus, https://www.sheret.com/plumbing and https://www.sheret.com/contact 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.

  • 14 internal pages checked

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

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 6 small tap targets

    6 of 30 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 “Cannot set properties of null (setting 'href')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 social proof

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

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

  • Only about 70 words

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

  • No form on the homepage

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

  • No risk reducer

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

2 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Register”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies (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.

  • 9 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on sheret.com, including 6 speed issues, 7 SEO issues and 4 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