Website review, no card needed

abacus.coop logo

abacus.coop website review

Visit site (opens in a new tab)Reviewed 31 October 202646 issues · 87 checks

This review found 46 issues worth fixing on abacus.coop, 22 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
3.4 s2.8 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.4 s
Jun 27, 20263.2 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
247 ms162 msMay 9Oct 24230 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026172 ms
May 16, 2026173 ms
May 23, 2026176 ms
May 30, 2026178 ms
Jun 6, 2026182 ms
Jun 13, 2026184 ms
Jun 20, 2026185 ms
Jun 27, 2026192 ms
Jul 4, 2026196 ms
Jul 11, 2026199 ms
Jul 18, 2026201 ms
Jul 25, 2026201 ms
Aug 1, 2026202 ms
Aug 8, 2026204 ms
Aug 15, 2026210 ms
Aug 22, 2026216 ms
Aug 29, 2026226 ms
Sep 5, 2026233 ms
Sep 12, 2026236 ms
Sep 19, 2026236 ms
Sep 26, 2026237 ms
Oct 3, 2026235 ms
Oct 10, 2026233 ms
Oct 17, 2026235 ms
Oct 24, 2026230 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 abacus.coop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abacus.coop at 0.6 s0.6 s
  2. abacus.coop at 1.3 s1.3 s
  3. abacus.coop at 1.9 s1.9 s
  4. abacus.coop at 2.6 s2.6 s
  5. abacus.coop at 3.2 s3.2 s
  6. abacus.coop at 3.9 s3.9 s
  7. abacus.coop at 4.5 s4.5 s
  8. abacus.coop at 5.1 s5.1 s

Speed

9 to fix31
  • Reduce unused JavaScript

    1.1 s · 601 KiB

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

  • Mobile performance score: 31

    31/100

    Your mobile performance score is 31. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8,850 HTML elements

    The page has 8,850 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, Cookiebot and TikTok and others), adding 1.2 MB and 1.2 s of main-thread time.

  • Google Tag Manager adds 617 ms

    617 ms

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

    450 ms · 76 KiB

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

  • Use efficient cache lifetimes

    350 ms · 167 KiB

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

  • Render-blocking requests

    500 ms

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

  • Main-thread work: 3.8 s

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

  • Improve image delivery

    150 ms · 126 KiB

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

  • 12 long tasks on the main thread

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

  • Minify CSS

    150 ms · 17 KiB

    17 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    29 KiB

    Polyfills for old browsers add 29 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: 57 ms

    57 ms

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

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 6.7 s

    6.7 s

    Real visitors wait 6.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.63

    0.63

    For real visitors the layout shifts by 0.63 (75th percentile). Good is under 0.1.

  • Real-user FCP: 5.8 s

    5.8 s

    Real visitors see the first content after 5.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 5.2 s

    5.2 s

    Real visitors wait 5.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 20.3 s

    20.3 s

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

  • Time to Interactive: 30.5 s

    30.5 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Cumulative Layout Shift: 0.614

    0.614

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

  • Real-user INP: 352 ms

    352 ms

    Real visitors wait 352 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

    +35%

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

  • 91 images without width and height

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

  • Total Blocking Time: 479 ms

    479 ms

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

1 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

2 to fix64
  • Page weight: 5.4 MB in 193 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 193 requests on a phone: fonts 2.7 MB (20), scripts 1.5 MB (52) and images 615 KiB (75). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Slider_512x327_calendaris_advent.png 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.5 g of CO₂ per visit

    1.54 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 185.0 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

10 to fixGoogle 7786
  • Certain ARIA roles must contain particular children (1 element)

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

  • 59 text elements with low contrast

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

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 52 images without alt text

    52 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 75 form fields without a label

    75 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 15 links without text

    15 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 8581
  • No H1 headline

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

  • No structured data

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

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 1,029 internal links, 18 external

    The homepage links to 1,029 pages on abacus.coop and 18 external pages.

5 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Abacus Cooperativa botiga online de productes i serveis culturals i educatius per a l'entorn familiar i la societat en …”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Abacus Cooperativa - Botiga Online”.

  • Canonical URL set

    The canonical URL is https://www.abacus.coop/.

  • 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.abacus.coop/sitemap_index.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.

  • No llms.txt

    There is no https://www.abacus.coop/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.

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

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.abacus.coop/ca/la-meva-cistella is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 194 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 1 page 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.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

4 to fixGoogle 9270
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=fede830d-340e-42f8-b1b5-daee14c0d733&referrer=&landingpage=https%3A%2F%2Fwww.abacus.coop%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%201.

  • 91 small tap targets

    91 of 177 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 “$ is not defined”.

  • 1 distorted image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • No call to action on the first screen

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

  • No social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 20,734 words of copy

    The homepage carries about 20,734 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “The Book”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and TikTok Pixel.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and TikTok Pixel (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.

  • 27 cookies set on arrival

    27

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

  • 31 other companies contacted

    Loading the homepage contacts 31 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 abacus.coop, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
45 open roles
Teams
Enterprise Service Desk-Healthcare (7), Enterprise Service Desk-Financial Services (6), SW Dev & DevOps (6), Cybersecurity (4)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on abacus.coop, including 22 speed issues, 4 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

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