Programmable

Website review, no card needed

robarnesen.no logo

robarnesen.no website review

Visit site (opens in a new tab)Reviewed 10 November 202616 issues · 57 checks

This review found 16 issues worth fixing on robarnesen.no, 5 of them high impact, across 57 checks. The most urgent: orphan list items. 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

90A

Closest competitors among Shopify stores

Compare side by side

One score from every part of this review. How it works

robarnesen.no (opens in a new tab)
Full-page screenshot of robarnesen.no (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. robarnesen.no at 0.4 s0.4 s
  2. robarnesen.no at 0.8 s0.8 s
  3. robarnesen.no at 1.1 s1.1 s
  4. robarnesen.no at 1.5 s1.5 s
  5. robarnesen.no at 1.9 s1.9 s
  6. robarnesen.no at 2.3 s2.3 s
  7. robarnesen.no at 2.6 s2.6 s
  8. robarnesen.no at 3.0 s3.0 s

Speed

2 to fix99

  • Render-blocking requests

    700 ms

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

  • Improve image delivery

    414 KiB

    4 images could be 414 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    102 KiB

    About 102 KiB of JavaScript is downloaded but never used on this page.

  • 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 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 36 KiB and 0 ms of main-thread time.

3 checks passed

  • Mobile performance score: 99

    99/100

    Your mobile performance score is 99. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.4 s

    A phone's processor spends 0.4 s on main-thread work while loading, 109 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

100

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

6 checks passed

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Vi hjelper norsk varehandel med å finne, utvikle og levere …”.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.7 s

    1.7 s

    The page is fully interactive after 1.7 s.

Images and page weight

2 to fix80

  • 4 images far larger than shown

    485 KiB

    4 images are downloaded at several times the size a phone draws them, for example kategori-tekstil-DdZfS4bQ.jpg at 1,200 px wide, shown at 169 px. Resized copies would save about 485 KiB.

  • 4 images in older formats

    4 images (590 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.2 g of CO₂ per visit

    0.24 g

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

2 checks passed

  • Page weight: 866 KiB in 17 requests

    866 KiB

    Your homepage downloads 866 KiB in 17 requests on a phone: images 592 KiB (4), scripts 207 KiB (8) and fonts 35 KiB (1). That is a lean page.

  • Images load when needed

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

Accessibility

2 to fixGoogle 9396

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

2 checks passed

  • Every image has alt text

    All 8 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 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 9285

  • Meta description is long (162 characters)

    Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (FAQPage and Organization) but with 1 problem, for example “Organization: url is not an absolute URL ("/")”.

  • No XML sitemap

    No XML sitemap at https://robarnesen.no/sitemap.xml, so Google discovers your pages only by following links.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

5 checks passed

  • One H1 headline

    Your main headline reads: “Vi gjør det enklere å utvikle lønnsomme konsepter”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Rob. Arnesen | Sortiment, sourcing og EMV for norsk varehandel”.

  • Canonical URL set

    The canonical URL is https://robarnesen.no/.

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

AI search readiness

1 to fix88

  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://robarnesen.no/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 (712 words), so crawlers that don't run JavaScript still read it.

Best practices

Google 100100

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50

  • 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 street address 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 704 words of visible text.

3 checks passed

  • 1 short form

    A short form (4 fields at most) is right on the homepage.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify;Shopify Plus;SparkLayer
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 16 issues on robarnesen.no, including 2 speed issues, 4 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

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