chunkys.com website review

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

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

About 377 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

11 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

7 third-party services load with your homepage (Google Tag Manager, theatertoolkit.com and Facebook and others), adding 8.6 MB and 736 ms of main-thread time.

Your mobile performance score is 51 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

theatertoolkit.com costs a phone 299 ms of main-thread work and 6.7 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.

About 71 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

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

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

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

tmdb.org costs a phone 0 ms of main-thread work and 1.2 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.

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

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

10 KiB could be saved by minifying JavaScript.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

8 long tasks block the main thread while loading, the longest for 148 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.

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

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

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

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

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

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

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

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

Your homepage downloads 8.8 MB in 111 requests on a phone: images 7.3 MB (73), scripts 876 KiB (24) and fonts 366 KiB (6). Under 2 MB keeps phones on slow connections fast.

Chunkys-LoyaltySign-Digital-0225.jpg weighs 1.6 MB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example Chunkys-LoyaltySign-Digital-0225.jpg at 1,920 px wide, shown at 294 px. Resized copies would save about 1.3 MB.

37 images (5.2 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.

7 images further down the page (2.4 MB) 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 2.50 g of CO₂e: 299.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

Some list items are not inside a list.

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

No XML sitemap at https://www.chunkys.com/sitemap.xml, so Google discovers your pages only by following links.

9 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 133 pages on chunkys.com and 7 external pages.

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.

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 /movie-theater/chunkysmanchester all use the title “Chunky's Cinema Pub Manchester | Movie Theater”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/movie-theater/chunkysmanchester/movies, /movie-theater/chunkysmanchester/coming-soon, /movie-theater/chunkysmanchester/upcoming-events, /movie-theater/chunkysmanchester/menu, /movie-theater/chunkysmanchester/food-specials and /movie-theater/chunkysmanchester/theater-rental and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

/movie-theater/chunkysmanchester/event-information and /movie-theater/chunkysmanchester/loyalty have no <h1> headline, so visitors and search engines get no clear main topic.

/movie-theater/chunkysmanchester/menu, /movie-theater/chunkysmanchester/food-specials, /movie-theater/chunkysmanchester/loyalty, /movie-theater/chunkysmanchester/newsletter and /movie-theater/chunkysmanchester/employment have 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 15 pages linked from your homepage (of 87 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Uncaught Error: [splide] A track/list element is missing.”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

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.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

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 648 words of visible text.

DMARC is set to p=none, so mail pretending to be chunkys.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Meta Pixel (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.

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

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.

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