Website review, no card needed

426.agency logo

426.agency website review

Visit site (opens in a new tab)Reviewed 10 November 202633 issues · 81 checks

This review found 33 issues worth fixing on 426.agency, 11 of them high impact, across 81 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

Full-page screenshot of 426.agency (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix81
  • Render-blocking requests

    1.1 s

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

  • Use efficient cache lifetimes

    1.9 MB

    13 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google CDN, Facebook and Hubspot and others), adding 1.2 MB and 963 ms of main-thread time.

  • Mobile performance score: 81

    81/100

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

  • Reduce unused CSS

    600 ms · 163 KiB

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

  • Reduce unused JavaScript

    624 KiB

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

  • Google CDN adds 515 ms

    515 ms

    Google CDN costs a phone 515 ms of main-thread work and 743 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.

  • Main-thread work: 3.6 s

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

  • 13 long tasks on the main thread

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

  • Improve image delivery

    253 KiB

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

  • 2,493 HTML elements

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

  • Legacy JavaScript

    74 KiB

    Polyfills for old browsers add 74 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: 5 ms

    5 ms

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

Core Web Vitals

4 to fix84
  • Time to Interactive: 15.9 s

    15.9 s

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

  • Total Blocking Time: 552 ms

    552 ms

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

  • Speed Index: 5.3 s

    5.3 s

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

  • 2 images without width and height

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

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

  • 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 “When things get technically complicated, we hit the ground …”.

  • Cumulative Layout Shift: 0.035

    0.035

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

Images and page weight

2 to fix60
  • Page weight: 5.1 MB in 127 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 127 requests on a phone: media 2.2 MB (1), scripts 1.5 MB (50) and images 681 KiB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    19 KiB

    1 image is downloaded at several times the size a phone draws it, for example 426-cso-stefanie-vaia-speaking-at-e-commerce-conference.jpg at 1,000 px wide, shown at 300 px. Resized copies would save about 19 KiB.

  • 1 image in older formats

    1 image (102 KiB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (102 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.44 g

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

Accessibility

10 to fixGoogle 7085
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 5 tap targets too small

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

  • 4 text elements with low contrast

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

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 50 images without alt text

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

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

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • 6 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

1 to fixGoogle 8598
  • 3 links crawlers can't follow

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

  • 458 internal links, 14 external

    The homepage links to 458 pages on 426.agency and 14 external pages.

8 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Technology partner for e-commerce, software development and system integration across Italy and the DACH region.”.

  • One H1 headline

    Your main headline reads: “Your Digital Upgrade”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Custom Software & E-Commerce Solutions | 426”.

  • Canonical URL set

    The canonical URL is https://www.426-upgrade.com/en.

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

  • 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.426-upgrade.com/de/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.426-upgrade.com/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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.426-upgrade.com/en/migration-shopware 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 78 found) and read each the way a search engine does.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (5 required). Every extra field lowers completion.

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

    The homepage carries about 822 words of visible text.

7 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “< CONTACT >”, “Contact” and “SUBSCRIBE TO NEWSLETTER”.

  • Social proof on the page

    Social proof on the homepage: 23 customer or partner logos and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

  • 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads HubSpot and Meta Pixel (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.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 9 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 426.agency, 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
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on 426.agency, including 15 speed issues, 1 SEO issue 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