Website review, no card needed

prideinnhotels.com logo

prideinnhotels.com website review

Visit site (opens in a new tab)Reviewed 29 October 202623 issues · 77 checks

This review found 23 issues worth fixing on prideinnhotels.com, 8 of them high impact, across 77 checks. The most urgent: fails Core Web Vitals for real visitors. 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
7.2 s4.0 sMay 9Oct 244.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.8 s
May 16, 20265.6 s
May 23, 20265.1 s
May 30, 20265.0 s
Jun 6, 20265.1 s
Jun 13, 20265.2 s
Jun 20, 20265.2 s
Jun 27, 20265.2 s
Jul 4, 20265.1 s
Jul 11, 20264.7 s
Jul 18, 20264.5 s
Jul 25, 20264.4 s
Aug 1, 20264.5 s
Aug 8, 20264.6 s
Aug 15, 20264.7 s
Aug 22, 20264.8 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.7 s
Sep 19, 20264.7 s
Sep 26, 20264.9 s
Oct 3, 20264.8 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
195 ms120 msMay 9Oct 24186 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026130 ms
May 16, 2026135 ms
May 23, 2026137 ms
May 30, 2026142 ms
Jun 6, 2026142 ms
Jun 13, 2026147 ms
Jun 20, 2026151 ms
Jun 27, 2026151 ms
Jul 4, 2026152 ms
Jul 11, 2026145 ms
Jul 18, 2026141 ms
Jul 25, 2026134 ms
Aug 1, 2026129 ms
Aug 8, 2026132 ms
Aug 15, 2026135 ms
Aug 22, 2026137 ms
Aug 29, 2026138 ms
Sep 5, 2026138 ms
Sep 12, 2026137 ms
Sep 19, 2026138 ms
Sep 26, 2026145 ms
Oct 3, 2026158 ms
Oct 10, 2026168 ms
Oct 17, 2026178 ms
Oct 24, 2026186 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 prideinnhotels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

94
  • Improve image delivery

    228 KiB

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

  • Reduce unused CSS

    19 KiB

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

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 16 ms of it running JavaScript. That is comfortably low.

  • Server response: 87 ms

    87 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.5 s

    5.5 s

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

  • Real-user FCP: 4.5 s

    4.5 s

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

  • Real-user TTFB: 3.7 s

    3.7 s

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

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

    +37%

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PrideInn Paradise is one of the best hotels in Mombasa, off…”.

8 checks passed
  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -24%

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

  • Time to Interactive: 3.0 s

    3.0 s

    The page is fully interactive after 3.0 s.

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Speed Index: 2.5 s

    2.5 s

    Visually, the page fills in at 2.5 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.021

    0.021

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 33 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 33 requests on a phone: images 3.9 MB (26), fonts 116 KiB (5) and HTML 46 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.15 g

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

9 to fixGoogle 8890
  • 15 text elements with low contrast

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

  • 8 tap targets too small

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

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

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

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

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 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 10085
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “Hotels in Nairobi | Hotels in Mombasa - PrideInn Hotels, Resorts & Camps”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“PrideInn Hotels, Resorts & Camps” and “World-class Amenities”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 58 internal links, 9 external

    The homepage links to 58 pages on prideinnhotels.com and 9 external pages.

5 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “PrideInn Hotels, Resorts & Camps, the best hotels in Kenya. Discover unparalleled hospitality and accommodations across…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, Hotel 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.prideinnhotels.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 contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.prideinnhotels.com/llms.txt (46 KiB, 199 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 3 pages without an H1

    https://www.prideinnhotels.com/contact-us, https://www.prideinnhotels.com/our-magazine and https://www.prideinnhotels.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.prideinnhotels.com/conferencing, https://www.prideinnhotels.com/weddings and https://www.prideinnhotels.com/contact-us took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 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.

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

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix89
  • 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.

  • 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 581 words of copy

    The homepage carries about 581 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: “BOOK NOW” and “CALL NOW”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact Us”, “BOOK NOW” and “BOOK DIRECTLY”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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
  • 4 trackers load before any consent

    4

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 prideinnhotels.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
Analytics
Google Analytics | Google Tag Manager
Hosting
Newfold Digital

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on prideinnhotels.com, including 6 speed issues, 3 SEO issues and 1 conversion gap. 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