Website review, no card needed
bigissue.com website review
Visit site (opens in a new tab)Reviewed 19 November 202632 issues · 83 checks
This review found 32 issues worth fixing on bigissue.com, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 188 ms |
| Jul 4, 2026 | 193 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 192 ms |
| Aug 1, 2026 | 186 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 204 ms |
| Aug 22, 2026 | 213 ms |
| Aug 29, 2026 | 218 ms |
| Sep 5, 2026 | 217 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 224 ms |
| Sep 26, 2026 | 228 ms |
| Oct 3, 2026 | 230 ms |
| Oct 10, 2026 | 233 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 234 ms |
| Oct 31, 2026 | 228 ms |
| Nov 7, 2026 | 225 ms |
| Nov 14, 2026 | 222 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.2 s
2.7 s
3.2 s
3.8 s
4.3 s
Speed
Render-blocking requests
1.2 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 7.0 s
A phone's processor spends 7.0 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6,137 HTML elements
The page has 6,137 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, intergient.com and Hubspot and others), adding 2.5 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 1,001 KiB41 files are served with short cache lifetimes, so returning visitors download them again (1,001 KiB).
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 608 ms
608 msGoogle Tag Manager costs a phone 608 ms of main-thread work and 692 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.
intergient.com adds 387 ms
387 msintergient.com costs a phone 387 ms of main-thread work and 483 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.
Reduce unused CSS
300 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 290 ms. During a long task the page ignores taps.
Hubspot adds 273 ms
273 msHubspot costs a phone 273 ms of main-thread work and 115 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.
Cookiebot adds 225 ms
225 msCookiebot costs a phone 225 ms of main-thread work and 468 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/Doubleclick Ads adds 133 ms
133 msGoogle/Doubleclick Ads costs a phone 133 ms of main-thread work and 304 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.
Improve image delivery
200 ms · 175 KiB4 images could be 175 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
90 KiBPolyfills for old browsers add 90 KiB JavaScript that modern phones do not need.
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: 29 ms
29 msYour server sent the HTML in 29 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 27.0 s
27.0 sThe page becomes fully interactive after 27.0 s. Good is under 3.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.3 s
4.3 sYour 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 “Grand Theft Auto VI protagonists Lucia Caminos and Jason Du…”.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 192 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 189 ms
189 msReal visitors wait 189 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 686 ms
686 msReal visitors wait 686 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 184 requests
3.7 MBYour homepage downloads 3.7 MB in 184 requests on a phone: scripts 3.0 MB (68), images 341 KiB (30) and other files 144 KiB (71). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
1743-GTA_Hero.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 1.0 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 50 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (9 characters)
Your title is only 9 characters: “Big Issue”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
110 internal links, 16 external
The homepage links to 110 pages on bigissue.com and 16 external pages.
6 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “The UK's number one street paper and social enterprise, giving people who are experiencing homelessness or who are vuln…”.
One H1 headline
Your main headline reads: “Top Stories”.
Canonical URL set
The canonical URL is https://www.bigissue.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage 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://www.bigissue.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.bigissue.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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,912 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages without a meta description
https://www.bigissue.com/news, https://www.bigissue.com/news/housing, https://www.bigissue.com/news/employment, https://www.bigissue.com/life/health, https://www.bigissue.com/news/environment and https://www.bigissue.com/news/politics have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Every page has an H1
Each page we checked has a main headline.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211042369&tm=gtm002&Ver=2&mid=adc3c4db-a1d3-4084-bd1b-a69e5077dee1&bo=1&sid=01a720e0e44711f18ac1115007b45fa5&vid=01a76aa0e44711f19c041f579bd4b1ce&vids=1&msclkid=N&pi=9.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
2 checks passed
Tap targets are thumb-sized
23 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 1,966 words of copy
The homepage carries about 1,966 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BUY A KIT” and “SUBSCRIBE”.
9 calls to action
The homepage has 9 calls to action, for example “Buy A Kit”, “Big Issue Shop” and “Subscribe to a local vendor”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 5 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
33 cookies set on arrival
33Opening the homepage sets 33 cookies, 8 of them by other companies (measured from a US location before any click).
69 other companies contacted
Loading the homepage contacts 69 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 bigissue.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
- Analytics
- Google Tag Manager
- Hosting
- WordPress.com
Company
- Founded
- 1991
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on bigissue.com, including 18 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.