Website review, no card needed

chaimsproaesthetics.com logo

chaimsproaesthetics.com website review

Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 83 checks

This review found 39 issues worth fixing on chaimsproaesthetics.com, 12 of them high impact, across 83 checks. The most urgent: page weight: 57.3 MB in 103 requests. 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
941 ms620 msMay 30Oct 24904 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026658 ms
Jun 6, 2026657 ms
Jul 11, 2026675 ms
Jul 18, 2026715 ms
Jul 25, 2026732 ms
Aug 1, 2026746 ms
Aug 8, 2026741 ms
Aug 15, 2026745 ms
Aug 22, 2026784 ms
Aug 29, 2026789 ms
Sep 5, 2026828 ms
Oct 24, 2026904 ms
Real-visitor tap response (INP)75th percentile, phones
77 ms69 msMay 30Aug 1571 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202670 ms
Jun 6, 202672 ms
Jul 25, 202676 ms
Aug 1, 202672 ms
Aug 8, 202672 ms
Aug 15, 202671 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 chaimsproaesthetics.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix80
  • Render-blocking requests

    1.2 s

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

  • Reduce unused JavaScript

    450 ms · 980 KiB

    About 980 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.

  • Mobile performance score: 80

    80/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Shopify and Other Google APIs/SDKs and others), adding 1.7 MB and 660 ms of main-thread time.

  • Google CDN adds 493 ms

    493 ms

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

  • Reduce unused CSS

    300 ms · 43 KiB

    About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 2.7 s

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

  • 11 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Improve image delivery

    9 KiB

    1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    5 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix77
  • Time to Interactive: 15.1 s

    15.1 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

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

  • Largest content (LCP) got 32% slower for real visitors

    +32%

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Total Blocking Time: 145 ms

    145 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 57.3 MB in 103 requests

    57.3 MB

    Your homepage downloads 57.3 MB in 103 requests on a phone: media 54.3 MB (3), scripts 1.6 MB (53) and other files 728 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • About 16.3 g of CO₂ per visit

    16.25 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fix62
  • Invalid ARIA attributes

    3 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (3 elements).

  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (2 elements).

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Hidden but focusable

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

  • ARIA input fields do not have accessible names

    ARIA input fields do not have accessible names (4 elements).

  • 3 links without text

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

  • 3 tap targets too small

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

  • 2 form fields without a label

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Headings skip levels

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

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (3 elements).

SEO

4 to fixGoogle 9279
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “ChaimsPro Medical Aesthetics : Professional Cosmetic Clinic in Toronto”.

  • Meta description is long (163 characters)

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

  • Structured data has 3 problems

    Structured data found ((untyped), BreadcrumbList, Organization and WebSite) but with 3 problems, for example “block has no @type”.

  • One H1 headline

    Your <h1> is empty.

  • 37 internal links, 15 external

    The homepage links to 37 pages on chaimsproaesthetics.com and 15 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://chaimsproaesthetics.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://chaimsproaesthetics.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix58
  • 3 linked pages are broken

    Your homepage links to https://chaimsproaesthetics.com/collections/online-store-products, https://chaimsproaesthetics.com/products/vitamin-c-brightening-whitening-soap and https://chaimsproaesthetics.com/blogs/news/meet-carmie, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://chaimsproaesthetics.com/pages/rules and https://chaimsproaesthetics.com/pages/copy-of-chaimspro-policy-guidelines all use the title “ChaimsPro Policy & Guidelines”. 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://chaimsproaesthetics.com/collections/services, https://chaimsproaesthetics.com/collections/facials-skincare, https://chaimsproaesthetics.com/collections/featured-products, https://chaimsproaesthetics.com/blogs/news, https://chaimsproaesthetics.com/pages/contact and https://chaimsproaesthetics.com/pages/about have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://chaimsproaesthetics.com/pages/about-us and https://chaimsproaesthetics.com/pages/rules have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

3 checks passed
  • 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://chaimsproaesthetics.com/.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

2 checks passed
  • Tap targets are thumb-sized

    13 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 70 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Phone number is not tap-to-call

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

  • About 1,018 words of copy

    The homepage carries about 1,018 words of visible text.

5 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Contact”, “Book An Appointment” and “BOOK AN APPOINTMENT”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 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.

  • 16 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on chaimsproaesthetics.com, including 12 speed issues, 4 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