Website review, no card needed

nishathotels.com logo

nishathotels.com website review

Visit site (opens in a new tab)Reviewed 1 November 202654 issues · 90 checks

This review found 54 issues worth fixing on nishathotels.com, 23 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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.5 s3.6 sMay 9Oct 247.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.4 s
May 23, 20264.8 s
May 30, 20265.2 s
Jun 6, 20265.5 s
Jun 13, 20265.6 s
Jun 20, 20265.8 s
Jun 27, 20265.7 s
Jul 4, 20265.7 s
Jul 11, 20265.8 s
Jul 18, 20265.7 s
Jul 25, 20265.6 s
Aug 1, 20265.6 s
Aug 8, 20265.5 s
Aug 15, 20265.6 s
Aug 22, 20265.8 s
Aug 29, 20265.7 s
Sep 5, 20265.9 s
Sep 12, 20266.2 s
Sep 19, 20266.3 s
Sep 26, 20266.6 s
Oct 3, 20266.5 s
Oct 10, 20266.3 s
Oct 17, 20266.1 s
Oct 24, 20267.0 s
Real-visitor tap response (INP)75th percentile, phones
251 ms147 msMay 9Oct 24239 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026159 ms
May 16, 2026171 ms
May 23, 2026181 ms
May 30, 2026184 ms
Jun 6, 2026191 ms
Jun 13, 2026188 ms
Jun 20, 2026192 ms
Jun 27, 2026202 ms
Jul 4, 2026205 ms
Jul 11, 2026214 ms
Jul 18, 2026210 ms
Jul 25, 2026212 ms
Aug 1, 2026224 ms
Aug 8, 2026221 ms
Aug 15, 2026226 ms
Aug 22, 2026225 ms
Aug 29, 2026208 ms
Sep 5, 2026217 ms
Sep 12, 2026209 ms
Sep 19, 2026213 ms
Sep 26, 2026221 ms
Oct 3, 2026215 ms
Oct 10, 2026222 ms
Oct 17, 2026221 ms
Oct 24, 2026239 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 nishathotels.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nishathotels.com at 1.1 s1.1 s
  2. nishathotels.com at 2.2 s2.2 s
  3. nishathotels.com at 3.3 s3.3 s
  4. nishathotels.com at 4.4 s4.4 s
  5. nishathotels.com at 5.5 s5.5 s
  6. nishathotels.com at 6.6 s6.6 s
  7. nishathotels.com at 7.7 s7.7 s
  8. nishathotels.com at 8.8 s8.8 s

Speed

13 to fix31
  • Use efficient cache lifetimes

    37.3 s · 7.0 MB

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

  • Reduce unused JavaScript

    16.5 s · 2.9 MB

    About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 16.5 s faster on a phone.

  • Render-blocking requests

    12.8 s

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

  • Reduce unused CSS

    10.6 s · 1.8 MB

    About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.6 s faster on a phone.

  • Improve image delivery

    7.5 s · 1.5 MB

    4 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.5 s faster on a phone.

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 5.3 s

    A phone's processor spends 5.3 s on main-thread work while loading, 3.1 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 Hotjar and others), adding 2.5 MB and 1.4 s of main-thread time.

  • Google Tag Manager adds 611 ms

    611 ms

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

  • Google CDN adds 472 ms

    472 ms

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

  • Legacy JavaScript

    300 ms · 59 KiB

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

  • 19 long tasks on the main thread

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

  • 2,782 HTML elements

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

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

    109 ms

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

Core Web Vitals

13 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: 7.9 s

    7.9 s

    Real visitors wait 7.9 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.

  • First Contentful Paint: 14.4 s

    14.4 s

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

  • Largest Contentful Paint: 54.3 s

    54.3 s

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

  • Speed Index: 17.1 s

    17.1 s

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

  • Time to Interactive: 54.3 s

    54.3 s

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

  • Total Blocking Time: 710 ms

    710 ms

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

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

    +39%

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

  • Largest content (LCP) got 57% slower for real visitors

    +57%

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.161

    0.161

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

  • 1 image without width and height

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

2 checks passed
  • Real-user INP: 174 ms

    174 ms

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

  • Real-user CLS: 0.08

    0.08

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

Images and page weight

4 to fix35
  • Page weight: 9.9 MB in 233 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 233 requests on a phone: scripts 5.1 MB (112), stylesheets 2.1 MB (54) and images 1.7 MB (23). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    BANQUET-REVEAL-GRID.png weighs 1.5 MB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (1.6 MB) 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.

  • 1 image far larger than shown

    77 KiB

    1 image is downloaded at several times the size a phone draws it, for example BANQUET-REVEAL-GRID.png at 1,080 px wide, shown at 351 px. Resized copies would save about 77 KiB.

  • About 2.8 g of CO₂ per visit

    2.81 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

11 to fixGoogle 7987
  • 16 buttons without a name

    16 buttons have no accessible name, so screen readers announce just “button”.

  • 16 tap targets too small

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

  • 3 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 33 images without alt text

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

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

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

  • 23 links without text

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

  • 8 form fields without a label

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

  • ARIA role should be appropriate for the element (6 elements)

    ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (6 elements)

    Elements marked as presentational should be consistently ignored: 6 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 7787
  • Meta description is long (182 characters)

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

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • 9 links with vague text

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

  • 92 internal links, 20 external

    The homepage links to 92 pages on nishathotels.com and 20 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Experience Serenity & Comfort”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Most Booked-Best 5 Star Hotels in Lahore | The Nishat Hotel”.

  • Canonical URL set

    The canonical URL is https://nishathotels.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://nishathotels.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://nishathotels.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.

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 7 pages without a meta description

    https://nishathotels.com/contact, https://nishathotels.com/testimonials, https://nishathotels.com/gallery, https://nishathotels.com/blogs, https://nishathotels.com/packages/johar-town and https://nishathotels.com/dining-offers/johar-town and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://nishathotels.com/catering, whose canonical is https://nishathotels.com/catering/johar-town. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://nishathotels.com/testimonials and https://nishathotels.com/pay-now have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://nishathotels.com/testimonials, https://nishathotels.com/dining/johar-town, https://nishathotels.com/well-ness, https://nishathotels.com/packages/johar-town and https://nishathotels.com/pay-now took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 9687
  • 2 small tap targets

    2 of 9 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 “reCAPTCHA has already been rendered in this element”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (4 required). Every extra field lowers completion.

  • About 3,114 words of copy

    The homepage carries about 3,114 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “CONTACT US”, “Book Now” and “Subscribe”.

  • Social proof on the page

    Social proof on the homepage: 3 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 5 email links.

  • 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, Hotjar and Microsoft Clarity 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 20 other companies contacted

    Loading the homepage contacts 20 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 nishathotels.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 | Microsoft Clarity
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on nishathotels.com, including 26 speed issues, 4 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