rsfsoft.com website review

About 361 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

Your mobile performance score is 60 (desktop: 96). Pages that score under 90 lose visitors before the first paint.

Google Maps costs a phone 289 ms of main-thread work and 506 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.

6 third-party services load with your homepage (Google Maps, Google Tag Manager and Other Google APIs/SDKs and others), adding 812 KiB and 486 ms of main-thread time.

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

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

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

About 30 KiB of CSS is downloaded but never applied on this page.

Desktop scores 96 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

5 KiB could be saved by minifying CSS.

Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “RSF SOFT We do not just design websites, we transform them …”.

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

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

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

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

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.

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

By the Sustainable Web Design model, a visit to your homepage emits about 0.39 g of CO₂e: 46.7 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.

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “RSF SOFT”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“RSF SOFT”, “” and “”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 48 pages on rsfsoft.com and 4 external pages.

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.

There is no https://rsfsoft.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.

https://rsfsoft.com/mobile-app, https://rsfsoft.com/web-development, https://rsfsoft.com/wordpress-development, https://rsfsoft.com/shopify, https://rsfsoft.com/seo-packages and https://rsfsoft.com/google-my-business-optimisation and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

2 of 6 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

3 images are served at too low a resolution for sharp phone screens.

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 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 365 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 5 cookies (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.