Website review, no card needed

justahotels.com logo

justahotels.com website review

Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 87 checks

This review found 40 issues worth fixing on justahotels.com, 10 of them high impact, across 87 checks. The most urgent: render-blocking 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
6.7 s4.2 sMay 16Oct 314.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20266.4 s
May 23, 20265.9 s
May 30, 20265.5 s
Jun 6, 20265.4 s
Jun 13, 20265.6 s
Jun 20, 20265.7 s
Jun 27, 20265.9 s
Jul 4, 20265.9 s
Jul 11, 20265.7 s
Jul 18, 20265.7 s
Jul 25, 20265.5 s
Aug 1, 20265.4 s
Aug 8, 20265.3 s
Aug 15, 20264.9 s
Aug 22, 20264.8 s
Aug 29, 20265.0 s
Sep 5, 20265.4 s
Sep 12, 20265.9 s
Sep 19, 20265.9 s
Sep 26, 20265.7 s
Oct 3, 20265.2 s
Oct 10, 20264.7 s
Oct 17, 20264.6 s
Oct 24, 20264.5 s
Oct 31, 20264.6 s
Real-visitor tap response (INP)75th percentile, phones
187 ms143 msMay 16Oct 31182 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026150 ms
May 23, 2026149 ms
May 30, 2026148 ms
Jun 6, 2026148 ms
Jun 13, 2026157 ms
Jun 20, 2026162 ms
Jun 27, 2026164 ms
Jul 4, 2026168 ms
Jul 11, 2026165 ms
Jul 18, 2026160 ms
Jul 25, 2026165 ms
Aug 1, 2026165 ms
Aug 8, 2026171 ms
Aug 15, 2026173 ms
Aug 22, 2026172 ms
Aug 29, 2026179 ms
Sep 5, 2026179 ms
Sep 12, 2026181 ms
Sep 19, 2026179 ms
Sep 26, 2026172 ms
Oct 3, 2026171 ms
Oct 10, 2026173 ms
Oct 17, 2026177 ms
Oct 24, 2026182 ms
Oct 31, 2026182 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 justahotels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. justahotels.com at 1.2 s1.2 s
  2. justahotels.com at 2.4 s2.4 s
  3. justahotels.com at 3.6 s3.6 s
  4. justahotels.com at 4.8 s4.8 s
  5. justahotels.com at 6.0 s6.0 s
  6. justahotels.com at 7.2 s7.2 s
  7. justahotels.com at 8.4 s8.4 s
  8. justahotels.com at 9.6 s9.6 s

Speed

9 to fix71
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    260 ms · 587 KiB

    About 587 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 260 ms faster on a phone.

  • Use efficient cache lifetimes

    345 KiB

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

  • Improve image delivery

    301 KiB

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

  • 5 long tasks on the main thread

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

  • Main-thread work: 2.7 s

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

  • Google Maps adds 194 ms

    194 ms

    Google Maps costs a phone 194 ms of main-thread work and 397 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,168 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (jQuery CDN, Google Maps and callnowbutton.com and others), adding 722 KiB and 460 ms of main-thread time.

  • Font display

    150 ms

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

  • Reduce unused CSS

    124 KiB

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    8 KiB

    Polyfills for old browsers add 8 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.

1 checks passed
  • Server response: 62 ms

    62 ms

    Your server sent the HTML in 62 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 LCP: 5.3 s

    5.3 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 2.3 s

    2.3 s

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

  • Speed Index: 14.3 s

    14.3 s

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

  • Time to Interactive: 10.7 s

    10.7 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user INP: 228 ms

    228 ms

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

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

    +22%

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

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

  • Total Blocking Time: 278 ms

    278 ms

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

  • 10 images without width and height

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

3 checks passed
  • 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 27% faster for real visitors

    -27%

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

2 to fix75
  • Page weight: 2.2 MB in 62 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 62 requests on a phone: scripts 1.1 MB (35), images 530 KiB (7) and fonts 314 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    274 KiB

    1 image is downloaded at several times the size a phone draws it, for example JHR-Website-Header-Logo-Gold-2560-x-1707-px-scaled.png at 2,560 px wide, shown at 150 px. Resized copies would save about 274 KiB.

  • 1 image in older formats

    1 image (283 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.

  • 1 image below the first screen load straight away

    1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

Accessibility

6 to fixGoogle 8389
  • 11 text elements with low contrast

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 34 elements on the page fail 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.

  • 30 form fields without a label

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

  • 7 links without text

    7 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 29 automated accessibility rules passed

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

    Your title is 78 characters, so Google will cut it off around 60: “Experience Luxury and Art at jüSTa Hotels & Resorts - Your Perfect Stay Awaits”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“What Makes Us jüSTa?” and “Stay Where Art Lives”). One clear main headline is easier for people and search engines.

  • Meta description is long (218 characters)

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

  • No social preview image

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

  • 3 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 95 internal links, 6 external

    The homepage links to 95 pages on justahotels.com and 6 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, LocalBusiness, Organization, 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.justahotels.com/sitemap_hotels.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, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 14 pages without an H1

    https://www.justahotels.com/hotels, https://www.justahotels.com/hotels/ahmedabad, https://www.justahotels.com/hotels/alwar, https://www.justahotels.com/hotels/bengaluru, https://www.justahotels.com/hotels/chittorgarh and https://www.justahotels.com/hotels/corbett and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://www.justahotels.com/hotels/goa took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 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”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 12-field form

    Your longest form asks for 12 fields (0 required). Every extra field lowers completion.

  • 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 map or directions link

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

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

    The homepage carries about 270 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “call CALL US” and “calendar BOOK NOW”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Sign Up”, “Contact” and “BOOK NOW”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

  • 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

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

  • 8 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 justahotels.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 Tag Manager
Hosting
WPX

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on justahotels.com, including 21 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