Website review, no card needed

hotel-wings.com logo

hotel-wings.com website review

Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 82 checks

This review found 36 issues worth fixing on hotel-wings.com, 17 of them high impact, across 82 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

Full-page screenshot of hotel-wings.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hotel-wings.com at 1.3 s1.3 s
  2. hotel-wings.com at 2.6 s2.6 s
  3. hotel-wings.com at 4.0 s4.0 s
  4. hotel-wings.com at 5.3 s5.3 s
  5. hotel-wings.com at 6.6 s6.6 s
  6. hotel-wings.com at 7.9 s7.9 s
  7. hotel-wings.com at 9.2 s9.2 s
  8. hotel-wings.com at 10.5 s10.5 s

Speed

4 to fix73
  • Render-blocking requests

    1.7 s

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

  • 5,325 HTML elements

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

  • Main-thread work: 5.3 s

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

  • Mobile performance score: 73

    73/100

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and Google Fonts), adding 348 KiB and 247 ms of main-thread time.

  • 10 long tasks on the main thread

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

  • Reduce unused JavaScript

    28 KiB

    About 28 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    16 KiB

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

  • Use efficient cache lifetimes

    5 KiB

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

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

4 to fix79
  • Speed Index: 10.3 s

    10.3 s

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

  • Largest Contentful Paint: 4.3 s

    4.3 s

    Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (4.6 s).

  • Time to Interactive: 6.7 s

    6.7 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 157 ms

    157 ms

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

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    bath1.png_1_1_b04f92f3-70a8-46ac-b8fe-e62def48e69d.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.47 g

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

3 checks passed
  • Page weight: 1.6 MB in 185 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 185 requests on a phone: other files 600 KiB (51), scripts 488 KiB (69) and images 240 KiB (19). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

15 to fixGoogle 7581
  • ARIA roles used must conform to valid values (2 elements)

    ARIA roles used must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

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

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

  • Hidden but focusable

    2 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 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.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 54 automated accessibility rules passed

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

SEO

5 to fixGoogle 9273
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (11 characters)

    Your title is only 11 characters: “hotel-wings”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “”). 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.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 208 internal links, 20 external

    The homepage links to 208 pages on hotel-wings.com and 20 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://hotel-wings.com/.

  • Structured data in place

    Structured data found: Organization 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://hotel-wings.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 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,611 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://hotel-wings.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://hotel-wings.com/collections/duvet-covers, https://hotel-wings.com/collections/duvet-inserts, https://hotel-wings.com/collections/pillow-inner, https://hotel-wings.com/collections/bed-runners, https://hotel-wings.com/collections/bedspreads and https://hotel-wings.com/collections/blankets and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://hotel-wings.com/collections/duvet-covers, https://hotel-wings.com/collections/duvet-inserts, https://hotel-wings.com/collections/pillow-inner, https://hotel-wings.com/collections/bed-runners, https://hotel-wings.com/collections/bedspreads and https://hotel-wings.com/collections/blankets and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://hotel-wings.com/collections/duvet-covers, https://hotel-wings.com/collections/duvet-inserts, https://hotel-wings.com/collections/pillow-inner and https://hotel-wings.com/collections/bed-runners took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

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

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getAttribute')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 471 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP DENIM”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop Denim”, “Shop elegentte” and “Shop now”.

  • 7 short forms

    7 short forms (2 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

  • 5 cookies set on arrival

    5

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 hotel-wings.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sami Wholesale · Pagefly Ai Page Builder

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on hotel-wings.com, including 8 speed issues, 5 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