swayapp.io website review

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

8 third-party services load with your homepage (hsappstatic.net, website-files.com and Hubspot and others), adding 3.9 MB and 591 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 900 ms.

website-files.com costs a phone 128 ms of main-thread work and 3.0 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.

hsappstatic.net costs a phone 338 ms of main-thread work and 715 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.

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

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

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

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

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

Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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.

Your homepage downloads 4.1 MB in 69 requests on a phone: images 2.8 MB (27), scripts 1.0 MB (20) and stylesheets 87 KiB (3). Under 2 MB keeps phones on slow connections fast.

69f456c45767e618084cc3f1_fiduciaire-csd_with_sway_finance.sv weighs 2.4 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 69f456c45767e618084cc3f1_fiduciaire-csd_with_sway_finance.sv at 937 px wide, shown at 198 px. Resized copies would save about 1.5 MB.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Structured data found (Organization, SoftwareApplication and WebSite) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 30 pages on swayapp.io and 31 external pages.

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

/, https://www.swayapp.io/fr and https://www.swayapp.io/de all use the title “Sway Finance - Automated accounting Supercharged.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.swayapp.io/clients-fiduciaries, https://www.swayapp.io/glossary, https://www.swayapp.io/terms/general-terms, https://www.swayapp.io/terms/privacy-policy and https://www.swayapp.io/terms/cookie-management-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.swayapp.io/fr and https://www.swayapp.io/de use the same meta description. A description written for each page earns more clicks.

https://www.swayapp.io/download, https://www.swayapp.io/faq, https://www.swayapp.io/contact, https://www.swayapp.io/blog, https://www.swayapp.io/glossary and https://www.swayapp.io/release-notes and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.swayapp.io/download and https://www.swayapp.io/jobs have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 513 words of visible text.

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

Opening the homepage sets 12 cookies, 4 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.