Website review, no card needed

thepinch.com logo

thepinch.com website review

Visit site (opens in a new tab)Reviewed 13 November 202632 issues · 88 checks

This review found 32 issues worth fixing on thepinch.com, 14 of them high impact, across 88 checks. The most urgent: page weight: 23.2 MB in 262 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
1.1 s862 msMay 23Nov 7895 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 2026947 ms
Jul 18, 2026933 ms
Jul 25, 2026933 ms
Aug 1, 2026900 ms
Aug 8, 2026971 ms
Aug 15, 2026932 ms
Aug 22, 2026992 ms
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 2026955 ms
Oct 24, 2026935 ms
Oct 31, 2026922 ms
Nov 7, 2026895 ms
Real-visitor tap response (INP)75th percentile, phones
134 ms81 msMay 23Nov 7128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202687 ms
Jun 13, 202687 ms
Jun 20, 202688 ms
Jun 27, 202692 ms
Jul 4, 202695 ms
Jul 11, 202695 ms
Jul 18, 202692 ms
Jul 25, 202690 ms
Aug 1, 202693 ms
Aug 8, 202688 ms
Aug 15, 202689 ms
Aug 22, 202692 ms
Aug 29, 202699 ms
Sep 5, 2026102 ms
Sep 12, 2026106 ms
Sep 19, 2026105 ms
Sep 26, 2026105 ms
Oct 3, 2026112 ms
Oct 10, 2026119 ms
Oct 17, 2026120 ms
Oct 24, 2026125 ms
Oct 31, 2026128 ms
Nov 7, 2026128 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 thepinch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thepinch.com at 0.5 s0.5 s
  2. thepinch.com at 1.0 s1.0 s
  3. thepinch.com at 1.5 s1.5 s
  4. thepinch.com at 2.0 s2.0 s
  5. thepinch.com at 2.5 s2.5 s
  6. thepinch.com at 2.9 s2.9 s
  7. thepinch.com at 3.4 s3.4 s
  8. thepinch.com at 3.9 s3.9 s

Speed

13 to fix35
  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 1.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 8.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Mapbox and others), adding 3.9 MB and 2.7 s of main-thread time.

  • Reduce unused JavaScript

    910 ms · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 1.2 MB

    128 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • Improve image delivery

    1.3 MB

    12 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    950 ms

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

  • 20 long tasks on the main thread

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

  • Google CDN adds 452 ms

    452 ms

    Google CDN costs a phone 452 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.

  • Mapbox adds 391 ms

    391 ms

    Mapbox costs a phone 391 ms of main-thread work and 468 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.

  • 2,439 HTML elements

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

  • Legacy JavaScript

    150 ms · 84 KiB

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

  • Minify JavaScript

    20 KiB

    20 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    13 KiB

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Speed Index: 16.1 s

    16.1 s

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

  • Time to Interactive: 43.6 s

    43.6 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies to ensure you get the best experi…”. Most of its time is element render delay (2.3 s).

  • Real-user INP: 231 ms

    231 ms

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

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

    +35%

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

6 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

  • 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: 372 ms

    372 ms

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

  • Largest content (LCP) got 17% faster for real visitors

    -17%

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

  • 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: 23.2 MB in 262 requests

    23.2 MB

    Your homepage downloads 23.2 MB in 262 requests on a phone: media 13.1 MB (1), images 4.6 MB (75) and scripts 4.0 MB (68). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (72 KiB) is 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.

  • About 6.6 g of CO₂ per visit

    6.58 g

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

2 checks passed
  • 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

3 to fixGoogle 9697
  • 21 text elements with low contrast

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

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

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

  • 5 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 78 images in the HTML carry an alt attribute.

  • 55 automated accessibility rules passed

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

SEO

3 to fixGoogle 9285
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 10 links with vague text

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

  • 58 internal links, 14 external

    The homepage links to 58 pages on thepinch.com and 14 external pages.

6 checks passed
  • Meta description: 88 characters

    Your meta description is 88 characters: “Settle into our modern, timeless retreat—refined and rooted in the spirit of Charleston.”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Boutique Hotel Charleston SC | The Pinch Charleston”.

  • Canonical URL set

    The canonical URL is https://www.thepinch.com/.

  • Structured data in place

    Structured data found: Hotel, WebPage and WebSite.

  • 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://www.thepinch.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, sameAs (social profiles), description and contact details; logo would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.thepinch.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix93
  • 2 pages share a title

    / and https://www.thepinch.com/events all use the title “Boutique Hotel Charleston SC | The Pinch Charleston”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages with very little text

    https://www.thepinch.com/accommodations, https://www.thepinch.com/gallery and https://www.thepinch.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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 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 meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=13006875&Ver=2&mid=0185e363-67c9-4d23-8cd8-7a664c294e7a&bo=1&sid=83c48490df1e11f1ac0f81b86ea8e6aa&vid=83c4c760df1e11f18cbf5166891227fb&vids=1&msclkid=N&pi=918639831&lg.

  • 6 small tap targets

    6 of 12 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”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No opening hours

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

  • No form on the homepage

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

  • About 832 words of copy

    The homepage carries about 832 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact”, “Sign Up” and “LEARN MORE”.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

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

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 7 of them by other companies (measured from a US location before any click).

  • 42 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

Upkeep, stack and company

Stack

CMS
HubSpot CMS
Analytics
Google Tag Manager
Hosting
HubSpot

Hiring

Hiring
75 open roles
Teams
Food & Beverage Operations (26), Hotel Operations (15), Corporate (1)
Job board
greenhouse

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 thepinch.com, including 21 speed issues and 3 SEO issues. 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