software-shop.com website review

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

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

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

Your mobile performance score is 45 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 1.7 MB and 1.2 s of main-thread time.

Google CDN costs a phone 546 ms of main-thread work and 771 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 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 520 ms faster on a phone.

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

Google Tag Manager costs a phone 303 ms of main-thread work and 455 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.

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

19 KiB could be saved by minifying JavaScript.

14 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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 10.1 MB in 217 requests on a phone: images 7.4 MB (150), scripts 1.8 MB (31) and fonts 422 KiB (8). Under 2 MB keeps phones on slow connections fast.

5 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example ABI_STATA_19_2_V3.jpg at 1,800 px wide, shown at 390 px. Resized copies would save about 570 KiB.

24 images (6.5 MB) 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.

18 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

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

Your title is only 13 characters: “Software Shop”. 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 (“X”, “Haz tu solicitud:” and “X”). One clear main headline is easier for people and search engines.

No XML sitemap at https://www.software-shop.com/sitemap, so Google discovers your pages only by following links.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 226 pages on software-shop.com and 37 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://software-shop.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.

/ and https://software-shop.com/portafolio-software all use the title “Software Shop”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://software-shop.com/productos/qualitative, https://software-shop.com/productos/quantitative and https://software-shop.com/productos/scientific use the same meta description. A description written for each page earns more clicks.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot set properties of null (setting 'href')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

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

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

Opening the homepage sets 14 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.