Website review, no card needed

salonsbyjc.com logo

salonsbyjc.com website review

Visit site (opens in a new tab)Reviewed 18 November 202639 issues · 79 checks

This review found 39 issues worth fixing on salonsbyjc.com, 12 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
3.7 s2.6 sMay 30Nov 143.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.9 s
Aug 1, 20262.8 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20263.0 s
Sep 5, 20263.0 s
Sep 12, 20263.0 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.3 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.6 s
Nov 7, 20263.6 s
Nov 14, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
247 ms150 msMay 30Nov 14228 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026161 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026167 ms
Jun 27, 2026168 ms
Jul 4, 2026172 ms
Jul 11, 2026179 ms
Jul 18, 2026187 ms
Jul 25, 2026195 ms
Aug 1, 2026196 ms
Aug 8, 2026204 ms
Aug 15, 2026213 ms
Aug 22, 2026220 ms
Aug 29, 2026224 ms
Sep 5, 2026228 ms
Sep 12, 2026227 ms
Sep 19, 2026223 ms
Sep 26, 2026227 ms
Oct 3, 2026228 ms
Oct 10, 2026229 ms
Oct 17, 2026232 ms
Oct 24, 2026236 ms
Oct 31, 2026235 ms
Nov 7, 2026234 ms
Nov 14, 2026228 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 salonsbyjc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix45
  • Reduce unused JavaScript

    4.6 s · 827 KiB

    About 827 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.

  • Render-blocking requests

    4.0 s

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

  • Use efficient cache lifetimes

    1.6 s · 308 KiB

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

  • Reduce unused CSS

    1.5 s · 292 KiB

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

  • Mobile performance score: 45

    45/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 1.9 MB and 1.3 s of main-thread time.

  • Google Tag Manager adds 984 ms

    984 ms

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

  • Legacy JavaScript

    300 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 300 ms faster on a phone.

  • Facebook adds 225 ms

    225 ms

    Facebook costs a phone 225 ms of main-thread work and 330 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.

  • Main-thread work: 2.3 s

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

  • Improve image delivery

    141 KiB

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

  • 14 long tasks on the main thread

    14 long tasks block the main thread while loading, the longest for 141 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.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    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-user FCP: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

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

  • Time to Interactive: 19.8 s

    19.8 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user INP: 226 ms

    226 ms

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

  • Tap response (INP) got 43% slower for real visitors

    +43%

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

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

    +31%

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Total Blocking Time: 588 ms

    588 ms

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

2 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 112 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 112 requests on a phone: scripts 2.1 MB (42), stylesheets 362 KiB (29) and images 168 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    76 KiB

    1 image is downloaded at several times the size a phone draws it, for example Copy-of-Salons-JC-14.webp at 1,735 px wide, shown at 312 px. Resized copies would save about 76 KiB.

  • About 0.8 g of CO₂ per visit

    0.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.82 g of CO₂e: 98.7 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 load when needed

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

Accessibility

1 to fixGoogle 9899
  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 7791
  • 2 H1 headlines

    There are 2 <h1> headlines (“Experience Extraordinary™” and “Experience Extraordinary™”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 24 internal links, 7 external

    The homepage links to 24 pages on salonsbyjc.com and 7 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Salon suite rental with 170+ locations nationwide for independent beauty professionals. Explore private studios, premiu…”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Salon Suite Rental | Salons by JC”.

  • Canonical URL set

    The canonical URL is https://salonsbyjc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • 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://salonsbyjc.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

2 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 (1,477 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix75
  • 2 linked pages hidden from search

    https://salonsbyjc.com/locations and https://salonsbyjc.com/salons are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages share a title

    https://salonsbyjc.com/locations and https://salonsbyjc.com/salons all use the title “- Salons by JC”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://salonsbyjc.com/locations, https://salonsbyjc.com/salons, https://salonsbyjc.com/our-story, https://salonsbyjc.com/coming-soon and https://salonsbyjc.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://salonsbyjc.com/locations and https://salonsbyjc.com/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

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

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

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

  • A 14-field form

    Your longest form asks for 14 fields (5 required). Every extra field lowers completion.

  • No opening hours

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

  • No map or directions link

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

  • About 738 words of copy

    The homepage carries about 738 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “LEARN MORE”, “[email protected]” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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
  • 4 trackers load before any consent

    4

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

  • 8 cookies set on arrival

    8

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

  • 17 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
1997
Headquarters
San Antonio

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on salonsbyjc.com, including 22 speed issues, 3 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