Website review, no card needed

solplast.com logo

solplast.com website review

Visit site (opens in a new tab)Reviewed 24 October 202639 issues · 88 checks

This review found 39 issues worth fixing on solplast.com, 12 of them high impact, across 88 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

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.3 sMay 2Oct 171.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.7 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.5 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.5 s
Oct 17, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
97 ms70 msJun 20Oct 1789 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 202687 ms
Jun 27, 202694 ms
Jul 4, 202691 ms
Jul 11, 202684 ms
Jul 18, 202680 ms
Jul 25, 202674 ms
Aug 1, 202673 ms
Aug 8, 202678 ms
Aug 29, 202686 ms
Sep 12, 202687 ms
Sep 19, 202684 ms
Sep 26, 202679 ms
Oct 3, 202690 ms
Oct 10, 202688 ms
Oct 17, 202689 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

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

Full-page screenshot of solplast.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix46
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 46

    46/100

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

  • Use efficient cache lifetimes

    850 ms · 1.2 MB

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

  • Improve image delivery

    100 ms · 980 KiB

    7 images could be 980 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Reduce unused JavaScript

    910 ms · 124 KiB

    About 124 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 910 ms faster on a phone.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Unpkg and JSDelivr CDN and others), adding 407 KiB and 169 ms of main-thread time.

  • Reduce unused CSS

    140 ms · 11 KiB

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

  • Font display

    150 ms

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

  • Minify JavaScript

    140 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

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

  • Phones get a much slower page than desktops

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 114 ms

    114 ms

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

Core Web Vitals

6 to fix100
  • Cumulative Layout Shift: 1.89

    1.89

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

  • Largest Contentful Paint: 7.9 s

    7.9 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

  • 30 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • Tap response (INP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 87 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +9%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.5 s

    1.5 s

    Real visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 89 ms

    89 ms

    Real visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.1 s

    1.1 s

    Real visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 591 ms

    591 ms

    Real visitors wait 591 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 56 ms

    56 ms

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    img-pagina-inicio.png weighs 640 KiB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    559 KiB

    6 images are downloaded at several times the size a phone draws them, for example img-pagina-inicio.png at 1,558 px wide, shown at 372 px. Resized copies would save about 559 KiB.

  • Page weight: 2.3 MB in 52 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 52 requests on a phone: images 1.9 MB (35), scripts 283 KiB (6) and fonts 146 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (1.7 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.

  • 6 images below the first screen load straight away

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

  • About 0.7 g of CO₂ per visit

    0.66 g

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

Accessibility

9 to fixGoogle 5983
  • 23 text elements with low contrast

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

  • 8 tap targets too small

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

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 7 links without text

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

  • Headings should not be empty (2 elements)

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

1 checks passed
  • 29 automated accessibility rules passed

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

SEO

7 to fixGoogle 6980
  • No structured data

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

  • No social preview image

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

  • No XML sitemap

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

  • 6 links with vague text

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

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

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

  • 38 internal links, 14 external

    The homepage links to 38 pages on solplast.com and 14 external pages.

4 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “At Solplast we cover from beginning to end all market needs with the most extensive and specialized universe of agricul…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Solplast - Plastics for Agriculture - Armando Álvarez Group”.

  • Canonical URL set

    The canonical URL is https://www.solplast.com/eng/home.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

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 (430 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 1 page without a meta description

    https://solplast.com/landing/en-congreso-uva-de-mesa.html has no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://solplast.com/eng/products/do-you-need-help, https://solplast.com/eng/news, https://solplast.com/eng/about-us/who-we-are, https://solplast.com/eng/products/productos-solplast, https://solplast.com/eng/sostenibilidad and https://solplast.com/eng/downloads/catalogues and 3 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 27 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.solplast.com/css=https://solplast.com/js/colorbox/colorbox.css,https://solplast.com/css/layouts.css,https://solplast.com/css/style.css?t=1…”.

  • 4 low-resolution images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

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

    The homepage carries about 496 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Contact us now” and “Download documents”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

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

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Eurocastalia
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on solplast.com, including 11 speed issues, 7 SEO issues and 1 conversion gap. 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