Website review, no card needed

saintpaulhotel.com logo

saintpaulhotel.com website review

Visit site (opens in a new tab)Reviewed 25 October 202638 issues · 87 checks

This review found 38 issues worth fixing on saintpaulhotel.com, 20 of them high impact, across 87 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
1.8 s1.1 sMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.6 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
287 ms97 msMay 2Oct 17228 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026119 ms
May 9, 2026160 ms
May 16, 2026173 ms
May 23, 2026218 ms
May 30, 2026163 ms
Jun 6, 2026162 ms
Jun 13, 2026164 ms
Jun 20, 2026149 ms
Jun 27, 2026153 ms
Jul 4, 2026144 ms
Jul 11, 2026144 ms
Jul 18, 2026139 ms
Jul 25, 2026145 ms
Aug 1, 2026158 ms
Aug 8, 2026158 ms
Aug 15, 2026166 ms
Aug 22, 2026166 ms
Aug 29, 2026175 ms
Sep 5, 2026210 ms
Sep 12, 2026207 ms
Sep 19, 2026179 ms
Sep 26, 2026251 ms
Oct 3, 2026265 ms
Oct 10, 2026217 ms
Oct 17, 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 saintpaulhotel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. saintpaulhotel.com at 1.1 s1.1 s
  2. saintpaulhotel.com at 2.2 s2.2 s
  3. saintpaulhotel.com at 3.3 s3.3 s
  4. saintpaulhotel.com at 4.4 s4.4 s
  5. saintpaulhotel.com at 5.5 s5.5 s
  6. saintpaulhotel.com at 6.7 s6.7 s
  7. saintpaulhotel.com at 7.8 s7.8 s
  8. saintpaulhotel.com at 8.9 s8.9 s

Speed

12 to fix27
  • Reduce unused JavaScript

    4.9 s · 941 KiB

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

  • Crazy Egg adds 4.3 s

    4.3 s

    Crazy Egg costs a phone 4.3 s of main-thread work and 466 KiB 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

    2.5 s

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

  • Use efficient cache lifetimes

    1.1 s · 379 KiB

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

  • Mobile performance score: 27

    27/100

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

  • Main-thread work: 9.1 s

    A phone's processor spends 9.1 s on main-thread work while loading, 6.6 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 (Crazy Egg, Google Tag Manager and Facebook and others), adding 2.2 MB and 5.8 s of main-thread time.

  • 18 long tasks on the main thread

    18 long tasks block the main thread while loading, the longest for 5.8 s. During a long task the page ignores taps.

  • Improve image delivery

    1.1 MB

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

  • Google Tag Manager adds 894 ms

    894 ms

    Google Tag Manager costs a phone 894 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

    450 ms · 54 KiB

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

  • 2,758 HTML elements

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

  • Font display

    150 ms

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

  • Legacy JavaScript

    15 KiB

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

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

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 33.1 s

    33.1 s

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

  • Total Blocking Time: 6.7 s

    6.7 s

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

  • Time to Interactive: 36.2 s

    36.2 s

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

  • Speed Index: 13.2 s

    13.2 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Real-user INP: 415 ms

    415 ms

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

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

    +59%

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

  • 4 images without width and height

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

6 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 503 ms

    503 ms

    Real visitors wait 503 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-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.1 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: 8.3 MB in 165 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 165 requests on a phone: images 4.8 MB (24), scripts 2.2 MB (62) and fonts 788 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 2.4 g of CO₂ per visit

    2.36 g

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

3 to fixGoogle 9095
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 46 text elements with low contrast

    46 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 (3 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 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 9289
  • Meta description is long (165 characters)

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

  • Structured data has 1 problem

    Structured data found (LocalBusiness, Organization, SiteNavigationElement and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

  • 323 internal links, 74 external

    The homepage links to 323 pages on saintpaulhotel.com and 74 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Plan Your Stay Today”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “The Saint Paul Hotel | Historic Luxury Hotel in Downtown St. Paul”.

  • Canonical URL set

    The canonical URL is https://www.saintpaulhotel.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://www.saintpaulhotel.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix50
  • 1 linked page is broken

    Your homepage links to https://www.saintpaulhotel.com/gift-cards, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without a title

    https://www.saintpaulhotel.com/dining/in-room-dining-menu, https://www.saintpaulhotel.com/amenities-menu, https://www.saintpaulhotel.com/the-saint-paul-hotel-wedding-brochure and https://www.saintpaulhotel.com/intimate-wedding-brochure have no <title>, so Google invents the link text in results.

  • 4 pages without a meta description

    https://www.saintpaulhotel.com/dining/in-room-dining-menu, https://www.saintpaulhotel.com/amenities-menu, https://www.saintpaulhotel.com/the-saint-paul-hotel-wedding-brochure and https://www.saintpaulhotel.com/intimate-wedding-brochure have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.saintpaulhotel.com/guestrooms-and-suites, https://www.saintpaulhotel.com/specials-and-packages, https://www.saintpaulhotel.com/dining/in-room-dining-menu, https://www.saintpaulhotel.com/amenities-menu, https://www.saintpaulhotel.com/weddings/reception-and-ceremony-spaces and https://www.saintpaulhotel.com/the-saint-paul-hotel-wedding-brochure and 1 other 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 48 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.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5174916&Ver=2&mid=67a78352-4f5f-40f9-b67d-70e3735e0816&bo=1&sid=6aa61620d07e11f19f941fc95ca5c50d&vid=6aa63870d07e11f18d79dbcfa7ba7f92&vids=1&msclkid=N&pi=918639831&lg=.

  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token ','”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix78
  • 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 opening hours

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

  • About 619 words of copy

    The homepage carries about 619 words of visible text.

7 checks passed
  • 32 calls to action

    The homepage has 32 calls to action, for example “Book Now”, “Inquire Now” and “Reserve”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 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

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, Meta Pixel and Microsoft Ads 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 (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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 saintpaulhotel.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

Company

Founded
1910

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on saintpaulhotel.com, including 21 speed issues, 3 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