Website review, no card needed
iba.ch website review
Visit site (opens in a new tab)Reviewed 25 October 202651 issues · 91 checks
This review found 51 issues worth fixing on iba.ch, 22 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
64DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.5 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 109 ms |
| May 9, 2026 | 108 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 110 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 107 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 110 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 109 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 110 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 109 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 109 ms |
| Oct 10, 2026 | 108 ms |
| Oct 17, 2026 | 110 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
Speed
Reduce unused JavaScript
9.6 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.6 s faster on a phone.
Improve image delivery
6.7 s · 3.9 MB28 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.7 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 19
19/100Your mobile performance score is 19 (desktop: 58). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Vimeo, Google Tag Manager and Facebook and others), adding 3.9 MB and 1.3 s of main-thread time.
Use efficient cache lifetimes
550 ms · 526 KiB31 files are served with short cache lifetimes, so returning visitors download them again (526 KiB).
Vimeo adds 533 ms
533 msVimeo costs a phone 533 ms of main-thread work and 3.1 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.
Google Tag Manager adds 417 ms
417 msGoogle Tag Manager costs a phone 417 ms of main-thread work and 359 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 311 ms. During a long task the page ignores taps.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 58 but mobile only 19. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 486 ms
486 msYour server sent the HTML in 486 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 CLS: 0.36
0.36For real visitors the layout shifts by 0.36 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 37.1 s
37.1 sYour largest element takes 37.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies und ähnliche Technologien, um das Nut…”.
Speed Index: 16.6 s
16.6 sVisually, the page fills in at 16.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 49.7 s
49.7 sThe page becomes fully interactive after 49.7 s. Good is under 3.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.403
0.403The layout shifts by 0.403 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 109 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 116 ms
116 msReal visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 10.8 MB in 250 requests
10.8 MBYour homepage downloads 10.8 MB in 250 requests on a phone: images 5.7 MB (62), scripts 4.0 MB (116) and fonts 597 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.
14 images in older formats
14 images (3.7 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.
2 images far larger than shown
157 KiB2 images are downloaded at several times the size a phone draws them, for example original.jpg at 1,186 px wide, shown at 390 px. Resized copies would save about 157 KiB.
1 image below the first screen load straight away
1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.1 g of CO₂ per visit
3.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.06 g of CO₂e: 367.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA progressbar nodes must have an accessible name (5 elements)
ARIA progressbar nodes must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
39 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: 39 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
50 internal links, 3 external
The homepage links to 50 pages on iba.ch and 3 external pages.
5 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Büromaterial für Firmenkunden online bestellen auf iba.ch: Profitieren Sie jetzt von günstigen B2B-Preisen & gratis Lie…”.
Title: 55 characters
Your title is a healthy 55 characters: “iba Büromaterial: günstiger Bürobedarf online bestellen”.
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://www.iba.ch/sitemapindex.xml.
AI search readiness
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.iba.ch/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 (281 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
/, https://www.iba.ch/ihre-vorteile and https://www.iba.ch/karriere all use the title “iba Büromaterial: günstiger Bürobedarf online bestellen”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages share a meta description
https://www.iba.ch/ihre-vorteile, https://www.iba.ch/kontakt, https://www.iba.ch/shop/de/papier-papierprodukte, https://www.iba.ch/shop/de/ordnen-archivieren, https://www.iba.ch/shop/de/schreibwaren and https://www.iba.ch/shop/de/buerotechnik and 7 others use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://www.iba.ch/shop/de/papier-papierprodukte, https://www.iba.ch/shop/de/ordnen-archivieren, https://www.iba.ch/shop/de/schreibwaren, https://www.iba.ch/shop/de/buerotechnik, https://www.iba.ch/shop/de/versenden-verpacken and https://www.iba.ch/shop/de/bueromoebel-bueroausstattung and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
5 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.
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=25006796&tm=gtm002&Ver=2&mid=5c65888f-efa9-46ce-aaa2-92a4c65dd74f&bo=1&sid=18486e60d05f11f1af4aa58e94234d34&vid=184889c0d05f11f193e88bbcc29538c7&vids=1&msclkid=N>m_t.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
23 of 24 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 330 words of copy
The homepage carries about 330 words of visible text.
2 checks passed
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 2 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 iba.ch, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on iba.ch, including 21 speed issues, 3 SEO issues and 5 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.