Website review, no card needed

plurbakery.com logo

plurbakery.com website review

Visit site (opens in a new tab)Reviewed 10 November 202623 issues · 70 checks

This review found 23 issues worth fixing on plurbakery.com, 5 of them high impact, across 70 checks. The most urgent: 31 text elements with low contrast. 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

Real-visitor load time (LCP)75th percentile, phones
2.0 s681 msMay 30Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.2 s
Jun 6, 20261.0 s
Jun 13, 2026896 ms
Jun 20, 2026863 ms
Jun 27, 2026906 ms
Jul 4, 2026837 ms
Jul 18, 20261.1 s
Jul 25, 2026927 ms
Aug 22, 20261.6 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Oct 10, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
160 ms75 msJun 6Aug 29150 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 202685 ms
Jun 13, 202686 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 18, 202686 ms
Jul 25, 202686 ms
Aug 22, 2026113 ms
Aug 29, 2026150 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

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

How it loaded on a phone

  1. plurbakery.com at 0.6 s0.6 s
  2. plurbakery.com at 1.1 s1.1 s
  3. plurbakery.com at 1.7 s1.7 s
  4. plurbakery.com at 2.3 s2.3 s
  5. plurbakery.com at 2.8 s2.8 s
  6. plurbakery.com at 3.4 s3.4 s
  7. plurbakery.com at 4.0 s4.0 s
  8. plurbakery.com at 4.6 s4.6 s

Speed

5 to fix74
  • Mobile performance score: 74

    74/100

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

  • Improve image delivery

    500 ms · 430 KiB

    12 images could be 430 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Render-blocking requests

    750 ms

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

  • Reduce unused JavaScript

    600 ms · 109 KiB

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

  • Main-thread work: 2.1 s

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

  • Reduce unused CSS

    150 ms · 14 KiB

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

  • 1 long task on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, nfcube.com and shop.app and others), adding 181 KiB and 22 ms of main-thread time.

  • Use efficient cache lifetimes

    14 KiB

    8 files are served with short cache lifetimes, so returning visitors download them again (14 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.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix68
  • Largest Contentful Paint: 7.7 s

    7.7 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

  • Tap response (INP) got 54% slower for real visitors

    +54%

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

  • Largest content (LCP) got 50% slower for real visitors

    +50%

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

  • Speed Index: 3.6 s

    3.6 s

    Visually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 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.

3 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 22 ms

    22 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.5 MB in 123 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 123 requests on a phone: images 1.4 MB (18), other files 622 KiB (58) and scripts 363 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    237 KiB

    2 images are downloaded at several times the size a phone draws them, for example wheat-poster.jpg at 1,600 px wide, shown at 23 px. Resized copies would save about 237 KiB.

  • 2 images in older formats

    2 images (171 KiB) 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.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9396
  • 31 text elements with low contrast

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

  • 1 tap target too small

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

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

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “Plúr Mill & Bakery · Sourdough, stoneground flour & Silín coffee · Borris, Co. Carlow”.

  • Meta description is short (18 characters)

    Your meta description is only 18 characters: “grow · mill · bake”. 70 to 160 characters is enough to sell the click.

  • 41 internal links, 7 external

    The homepage links to 41 pages on plurbakery.com and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “We growwe millwe bake”.

  • Canonical URL set

    The canonical URL is https://plur.ie/.

  • Structured data in place

    Structured data found: Bakery.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://plur.ie/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • llms.txt published

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

Other pages

1 to fix98
  • 5 pages share a meta description

    https://plur.ie/collections/all, https://plur.ie/products/tshirt, https://plur.ie/products/kinto-scs-cotton-paper-filter-4cups, https://plur.ie/policies/terms-of-service and https://plur.ie/policies/privacy-policy use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • No social proof

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

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

    The homepage carries about 784 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE FLOUR”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Shop the flour” and “Shop Silín”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 plurbakery.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

nfcube.com

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 23 issues on plurbakery.com, including 10 speed issues, 2 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