Website review, no card needed

hushr.app logo

hushr.app website review

Visit site (opens in a new tab)Reviewed 13 November 202627 issues · 51 checks

This review found 27 issues worth fixing on hushr.app, 10 of them high impact, across 51 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

Full-page screenshot of hushr.app (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hushr.app at 0.6 s0.6 s
  2. hushr.app at 1.2 s1.2 s
  3. hushr.app at 1.8 s1.8 s
  4. hushr.app at 2.5 s2.5 s
  5. hushr.app at 3.1 s3.1 s
  6. hushr.app at 3.7 s3.7 s
  7. hushr.app at 4.3 s4.3 s
  8. hushr.app at 4.9 s4.9 s

Speed

7 to fix56
  • Use efficient cache lifetimes

    17.8 s · 3.8 MB

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

  • Improve image delivery

    7.1 s · 1.6 MB

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

  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.7 s · 356 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    770 ms · 165 KiB

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

  • Minify CSS

    310 ms · 65 KiB

    65 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 36 KiB

    36 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 77 KiB and 1 ms of main-thread time.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix67
  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “helps babies fall asleep. Calms down crying babies instantl…”.

  • First Contentful Paint: 7.2 s

    7.2 s

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

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • 35 images without width and height

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

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 18 ms

    18 ms

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

Images and page weight

1 to fix50
  • Page weight: 3.8 MB in 101 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 101 requests on a phone: images 2.3 MB (23), scripts 1.1 MB (21) and stylesheets 406 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

Accessibility

1 to fix90
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • No main landmark

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

  • Headings skip levels

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

SEO

10 to fixGoogle 9155
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (28 characters)

    Your title is only 28 characters: “Hushr - Help Your Baby Sleep”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (28 characters)

    Your meta description is only 28 characters: “Hushr - Help Your Baby Sleep”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://hushr.app/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at hushr.app/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

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

  • No favicon declared

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

  • No X (Twitter) card tag

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

AI search readiness

1 to fix83
  • 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://hushr.app/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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

1 to fixGoogle 9693
  • 40 console errors

    40 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88
  • 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 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 838 words of copy

    The homepage carries about 838 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact us at: [email protected]”.

  • Social proof on the page

    Social proof on the homepage: 10 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

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 hushr.app, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2019.

Stack

Framework
jQuery
Hosting
IONOS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on hushr.app, including 12 speed issues, 10 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