tryhungry.com website review

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

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

8 third-party services load with your homepage (Google Tag Manager, TrackJS and Hubspot and others), adding 851 KiB and 564 ms of main-thread time.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

Your homepage downloads 2.2 MB in 92 requests on a phone: scripts 1.0 MB (38), images 946 KiB (34) and other files 123 KiB (10). Under 2 MB keeps phones on slow connections fast.

12 images further down the page (618 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Your title is 84 characters, so Google will cut it off around 60: “HUNGRY-A platform for workplace food-catering, group order events, snacks and pantry”.

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

The homepage links to 16 pages on tryhungry.com and 6 external pages.

The HTML your server sends has 508 of the 978 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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

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

/ and /marketplace all use the title “HUNGRY-A platform for workplace food-catering, group order events, sn…”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/terms-and-privacy and /press use the same meta description. A description written for each page earns more clicks.

/marketplace has no <h1> headline, so visitors and search engines get no clear main topic.

/terms-and-privacy has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of …”.

Large scripts ship without source maps.

1 link from your homepage to your own site is broken, for example https://tryhungry.com/cdn-cgi/l/email-protection (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

tryhungry.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

tryhungry.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 978 words of visible text.

DMARC is set to p=none, so mail pretending to be tryhungry.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 7 cookies (measured from a US location before any click).

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