Programmable

Website review, no card needed

inriver.se logo

inriver.se website review

Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 79 checks

This review found 24 issues worth fixing on inriver.se, 9 of them high impact, across 79 checks. The most urgent: render-blocking requests. 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

Site score

85B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
4.9 s2.8 sMay 16Oct 313.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.5 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.5 s
Jun 27, 20263.7 s
Jul 4, 20263.8 s
Jul 11, 20264.1 s
Jul 18, 20264.2 s
Jul 25, 20264.2 s
Aug 1, 20264.7 s
Aug 8, 20264.6 s
Aug 15, 20264.4 s
Aug 22, 20264.2 s
Aug 29, 20263.5 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.5 s
Oct 3, 20263.9 s
Oct 10, 20264.0 s
Oct 17, 20263.9 s
Oct 24, 20263.7 s
Oct 31, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
131 ms90 msMay 16Oct 31102 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026126 ms
May 23, 2026126 ms
May 30, 2026116 ms
Jun 6, 2026113 ms
Jun 13, 202699 ms
Jun 20, 202695 ms
Jun 27, 202696 ms
Jul 4, 2026101 ms
Jul 11, 2026101 ms
Jul 18, 2026103 ms
Jul 25, 2026115 ms
Aug 1, 2026115 ms
Aug 8, 2026112 ms
Aug 15, 2026110 ms
Aug 22, 2026105 ms
Aug 29, 2026105 ms
Sep 5, 2026102 ms
Sep 12, 2026102 ms
Sep 19, 2026102 ms
Sep 26, 2026104 ms
Oct 3, 2026117 ms
Oct 10, 2026117 ms
Oct 17, 2026111 ms
Oct 24, 2026106 ms
Oct 31, 2026102 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

www.inriver.com (opens in a new tab)
Full-page screenshot of inriver.se (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. inriver.se at 0.6 s0.6 s
  2. inriver.se at 1.2 s1.2 s
  3. inriver.se at 1.8 s1.8 s
  4. inriver.se at 2.4 s2.4 s
  5. inriver.se at 3.0 s3.0 s
  6. inriver.se at 3.6 s3.6 s
  7. inriver.se at 4.2 s4.2 s
  8. inriver.se at 4.8 s4.8 s

Speed

8 to fix77

  • Render-blocking requests

    1.3 s

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

  • Main-thread work: 4.5 s

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

  • Mobile performance score: 77

    77/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Cookiebot and VWO and others), adding 822 KiB and 673 ms of main-thread time.

  • Google Tag Manager adds 485 ms

    485 ms

    Google Tag Manager costs a phone 485 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.

  • Reduce unused JavaScript

    150 ms · 322 KiB

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

  • 11 long tasks on the main thread

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

  • 2,777 HTML elements

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

  • Reduce unused CSS

    150 ms · 45 KiB

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

  • Use efficient cache lifetimes

    51 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

9 to fix67

  • 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 FCP: 3.0 s

    3.0 s

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

  • Time to Interactive: 8.2 s

    8.2 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

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

  • Total Blocking Time: 442 ms

    442 ms

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bring your product information into the AI era”.

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

4 checks passed

  • Real-user INP: 101 ms

    101 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • About 0.4 g of CO₂ per visit

    0.36 g

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

4 checks passed

  • Page weight: 1.3 MB in 39 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 39 requests on a phone: scripts 767 KiB (12), other files 243 KiB (11) and images 122 KiB (10). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9291

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed

  • Every image has alt text

    All 17 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100

  • 97 internal links, 3 external

    The homepage links to 97 pages on inriver.se and 3 external pages.

8 checks passed

  • Meta description: 122 characters

    Your meta description is 122 characters: “Inriver is the AI-powered PIM that takes on the work complex product data creates - so launches move in weeks, not mont…”.

  • One H1 headline

    Your main headline reads: “Bring your product information into the AI era”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Inriver PIM Software: #1 Product Information Management Solution”.

  • Canonical URL set

    The canonical URL is https://www.inriver.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and WebPage.

  • 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.inriver.com/sitemap_index.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,507 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.inriver.com/llms.txt (7 KiB, 11 links), a plain-text guide to the site for AI tools.

Other pages

100

  • 5 pages slow to respond

    https://www.inriver.com/product/inspire-ai, https://www.inriver.com/product/brand-store, https://www.inriver.com/product/print-publish, https://www.inriver.com/product/syndicate-advance and https://www.inriver.com/solution/product-data-governance took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 55 found) 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

Google 100100
3 checks passed

  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92

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

    The homepage carries about 1,401 words of visible text.

5 checks passed

  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a demo”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Book a demo”, “Pricing plans” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos and “Trusted by 1,600+ brands”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 inriver.se, 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
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fouredge AB

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on inriver.se, including 17 speed issues and 1 conversion gap. 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