Website review, no card needed

saasenergypuebla.com logo

saasenergypuebla.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 72 checks

This review found 33 issues worth fixing on saasenergypuebla.com, 12 of them high impact, across 72 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
12.2 s9.1 sMay 23Nov 710.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 202610.1 s
May 30, 202610.1 s
Jun 6, 20269.5 s
Jun 13, 20269.5 s
Jun 20, 202610.4 s
Jun 27, 202610.4 s
Jul 4, 202610.7 s
Jul 11, 202611.4 s
Aug 1, 202611.0 s
Aug 15, 202611.8 s
Aug 22, 202611.8 s
Sep 26, 202610.4 s
Oct 3, 202611.0 s
Oct 17, 20269.9 s
Nov 7, 202610.0 s

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 saasenergypuebla.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix69
  • Render-blocking requests

    3.8 s

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

  • Improve image delivery

    1.1 s · 1.1 MB

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

  • Mobile performance score: 69

    69/100

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

  • Font display

    850 ms

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

  • Reduce unused CSS

    600 ms · 92 KiB

    About 92 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

    450 ms · 106 KiB

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

  • Use efficient cache lifetimes

    150 ms · 59 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Analytics and trustindex.io and others), adding 291 KiB and 113 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 89 ms. During a long task the page ignores taps.

  • 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: 1.1 s

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

  • Server response: 105 ms

    105 ms

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

Core Web Vitals

9 to fix50
  • Fails Core Web Vitals for real visitors

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

  • Real-user LCP: 10.0 s

    10.0 s

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

  • Real-user FCP: 8.9 s

    8.9 s

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

  • Real-user TTFB: 5.2 s

    5.2 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Contáctanos”.

  • Time to Interactive: 9.4 s

    9.4 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.024

    0.024

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

  • Total Blocking Time: 39 ms

    39 ms

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

Images and page weight

1 to fix67
  • Page weight: 2.8 MB in 160 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 160 requests on a phone: images 1.5 MB (23), scripts 543 KiB (62) and fonts 440 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.79 g

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

Accessibility

6 to fixGoogle 8475
  • No main landmark

    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)

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

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Frames without titles

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 63 images in the HTML carry an alt attribute.

  • 5 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8572
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 98 internal links, 20 external

    The homepage links to 98 pages on saasenergypuebla.com and 20 external pages.

4 checks passed
  • Title: 51 characters

    Your title is a healthy 51 characters: “Saas Energy – Tu Web Especializada en Energía Solar”.

  • Canonical URL set

    The canonical URL is https://saasenergypuebla.com/.

  • 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://saasenergypuebla.com/wp-sitemap.xml.

AI search readiness

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

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://saasenergypuebla.com/blog, https://saasenergypuebla.com/sistema-solar-interconectado, https://saasenergypuebla.com/sistema-fotovoltaico-aislado, https://saasenergypuebla.com/bombeo-de-agua-solar, https://saasenergypuebla.com/iluminacion-solar-fotovoltaica and https://saasenergypuebla.com/contacto and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://saasenergypuebla.com/tienda, https://saasenergypuebla.com/quienes-somos, https://saasenergypuebla.com/categoria-producto/kits-bombeo-solar-sumergible, https://saasenergypuebla.com/categoria-producto/bombas-solares-de-superficie, https://saasenergypuebla.com/categoria-producto/kits-bombeo-solar-superficie and https://saasenergypuebla.com/videos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No calls to action

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

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

    The homepage carries about 716 words of visible text.

4 checks passed
  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks and 36 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 saasenergypuebla.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
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
Asn Xtudionet Xnet Core Sl

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 saasenergypuebla.com, including 15 speed issues, 5 SEO issues 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