Website review, no card needed

beauporthotel.com logo

beauporthotel.com website review

Visit site (opens in a new tab)Reviewed 24 October 202642 issues · 88 checks

This review found 42 issues worth fixing on beauporthotel.com, 15 of them high impact, across 88 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
2.0 s1.6 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.8 s
Sep 26, 20261.9 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
148 ms124 msMay 2Oct 17137 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026145 ms
May 9, 2026138 ms
May 16, 2026136 ms
May 23, 2026135 ms
May 30, 2026138 ms
Jun 6, 2026138 ms
Jun 13, 2026138 ms
Jun 20, 2026136 ms
Jun 27, 2026134 ms
Jul 4, 2026133 ms
Jul 11, 2026135 ms
Jul 18, 2026132 ms
Jul 25, 2026131 ms
Aug 1, 2026129 ms
Aug 8, 2026127 ms
Aug 15, 2026127 ms
Aug 22, 2026128 ms
Aug 29, 2026130 ms
Sep 5, 2026135 ms
Sep 12, 2026136 ms
Sep 19, 2026130 ms
Sep 26, 2026129 ms
Oct 3, 2026129 ms
Oct 10, 2026131 ms
Oct 17, 2026137 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 beauporthotel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. beauporthotel.com at 0.4 s0.4 s
  2. beauporthotel.com at 0.8 s0.8 s
  3. beauporthotel.com at 1.2 s1.2 s
  4. beauporthotel.com at 1.6 s1.6 s
  5. beauporthotel.com at 2.0 s2.0 s
  6. beauporthotel.com at 2.4 s2.4 s
  7. beauporthotel.com at 2.8 s2.8 s
  8. beauporthotel.com at 3.1 s3.1 s

Speed

10 to fix36
  • Reduce unused JavaScript

    7.1 s · 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 7.1 s faster on a phone.

  • Render-blocking requests

    3.0 s

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

  • Reduce unused CSS

    1.1 s · 238 KiB

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

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36 (desktop: 43). 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, YouTube and videopolis.com and others), adding 3.0 MB and 1.6 s of main-thread time.

  • Google Tag Manager adds 688 ms

    688 ms

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

  • YouTube adds 380 ms

    380 ms

    YouTube costs a phone 380 ms of main-thread work and 985 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.

  • Legacy JavaScript

    350 ms · 60 KiB

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

  • Main-thread work: 3.8 s

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

  • Google Maps adds 179 ms

    179 ms

    Google Maps costs a phone 179 ms of main-thread work and 472 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.

  • Use efficient cache lifetimes

    150 ms · 63 KiB

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

  • 16 long tasks on the main thread

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

  • Improve image delivery

    17 KiB

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

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

    5 ms

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

Core Web Vitals

10 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 CLS: 0.26

    0.26

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

  • First Contentful Paint: 15.6 s

    15.6 s

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

  • Largest Contentful Paint: 24.1 s

    24.1 s

    Your largest element takes 24.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bed, comfy chair with lamp at Beauport Hotel Gloucester”.

  • Speed Index: 15.6 s

    15.6 s

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

  • Time to Interactive: 29.0 s

    29.0 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Cumulative Layout Shift: 0.242

    0.242

    The layout shifts by 0.242 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 294 ms

    294 ms

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user INP: 137 ms

    137 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 635 ms

    635 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.0 MB in 131 requests

    5.0 MB

    Your homepage downloads 5.0 MB in 131 requests on a phone: scripts 3.3 MB (60), images 1.2 MB (19) and stylesheets 226 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (186 KiB) 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.

  • 4 images below the first screen load straight away

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

  • About 1.4 g of CO₂ per visit

    1.40 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 9593
  • Images must have alternative text (4 elements)

    Images must have alternative text: 4 elements on the page fail this check, rated critical by axe-core.

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 8572
  • 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: “Beauport Hotel Gloucester | Gloucester MA Hotels | On The Oceanfront”.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList and Hotel) but with 1 problem, for example “Hotel: sameAs is an empty list”.

  • No social preview image

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

  • Only 3 internal links

    The homepage links to only 3 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

4 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “With a picturesque oceanfront location, upscale amenities & unforgettable hospitality, Beauport Hotel Gloucester is the…”.

  • Canonical URL set

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

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

AI search readiness

2 to fix75
  • Some text only appears after JavaScript runs

    43%

    The HTML your server sends has 115 of the 265 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. 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://www.beauporthotel.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

1 to fix95
  • 3 pages without an H1

    https://www.beauporthotel.com/rooms-suites, https://www.beauporthotel.com/weddings and https://www.beauporthotel.com/meetings-events have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.beauporthotel.com/meetings-events has 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.

  • 3 internal pages checked

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

6 checks passed
  • Linked pages load

    All 3 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 3 pages that loaded have a meta description.

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

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 9 third-party cookies

    9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 small tap targets

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

  • About 265 words of copy

    The homepage carries about 265 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “call us at9782820008” and “BOOK NOW”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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

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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 1 of them by other companies (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 beauporthotel.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 42 issues on beauporthotel.com, including 20 speed issues, 6 SEO issues and 3 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