Website review, no card needed

sanjorgecc.com.mx logo

sanjorgecc.com.mx website review

Visit site (opens in a new tab)Reviewed 24 October 202644 issues · 61 checks

This review found 44 issues worth fixing on sanjorgecc.com.mx, 17 of them high impact, across 61 checks. The most urgent: reduce unused CSS. 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
5.9 s3.7 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.0 s
May 9, 20265.3 s
May 16, 20265.5 s
May 23, 20265.6 s
May 30, 20265.7 s
Jun 6, 20265.7 s
Jun 13, 20265.4 s
Jun 20, 20265.1 s
Jun 27, 20264.6 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.0 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.0 s
Aug 29, 20264.0 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.1 s
Oct 3, 20264.0 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
451 ms271 msMay 2Oct 17430 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026296 ms
May 9, 2026292 ms
May 16, 2026302 ms
May 23, 2026305 ms
May 30, 2026321 ms
Jun 6, 2026320 ms
Jun 13, 2026326 ms
Jun 20, 2026346 ms
Jun 27, 2026349 ms
Jul 4, 2026385 ms
Jul 11, 2026365 ms
Jul 18, 2026370 ms
Jul 25, 2026357 ms
Aug 1, 2026339 ms
Aug 8, 2026348 ms
Aug 15, 2026350 ms
Aug 22, 2026377 ms
Aug 29, 2026395 ms
Sep 5, 2026404 ms
Sep 12, 2026380 ms
Sep 19, 2026382 ms
Sep 26, 2026380 ms
Oct 3, 2026389 ms
Oct 10, 2026412 ms
Oct 17, 2026430 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 sanjorgecc.com.mx (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sanjorgecc.com.mx at 1.5 s1.5 s
  2. sanjorgecc.com.mx at 3.1 s3.1 s
  3. sanjorgecc.com.mx at 4.6 s4.6 s
  4. sanjorgecc.com.mx at 6.1 s6.1 s
  5. sanjorgecc.com.mx at 7.7 s7.7 s
  6. sanjorgecc.com.mx at 9.2 s9.2 s
  7. sanjorgecc.com.mx at 10.7 s10.7 s
  8. sanjorgecc.com.mx at 12.3 s12.3 s

Speed

6 to fix50
  • Reduce unused CSS

    8.6 s · 1.5 MB

    About 1.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.6 s faster on a phone.

  • Reduce unused JavaScript

    6.1 s · 1.4 MB

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

  • Mobile performance score: 50

    50/100

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

  • Avoid multiple page redirects

    756 ms

    The page goes through 1 redirect before it starts loading, costing about 756 ms. Link and advertise the final URL directly.

  • Minify CSS

    450 ms · 88 KiB

    88 KiB could be saved by minifying CSS.

  • Main-thread work: 2.3 s

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

  • 8 long tasks on the main thread

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

1 checks passed
  • Server response: 63 ms

    63 ms

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

Core Web Vitals

11 to fix33
  • 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: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • First Contentful Paint: 12.8 s

    12.8 s

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

  • Largest Contentful Paint: 30.3 s

    30.3 s

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

  • Speed Index: 16.9 s

    16.9 s

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

  • Time to Interactive: 41.7 s

    41.7 s

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

  • Real-user INP: 438 ms

    438 ms

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

  • Tap response (INP) got 43% slower for real visitors

    +43%

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

  • Total Blocking Time: 229 ms

    229 ms

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

  • 5 images without width and height

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

4 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Real-user TTFB: 352 ms

    352 ms

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

  • Largest content (LCP) got 23% faster for real visitors

    -23%

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

  • Cumulative Layout Shift: 0.07

    0.07

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

Images and page weight

1 to fix33
  • Page weight: 7.8 MB in 146 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 146 requests on a phone: scripts 2.9 MB (57), images 2.7 MB (29) and stylesheets 1.6 MB (34). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.20 g

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

Accessibility

5 to fixGoogle 8470
  • Unlabelled dropdowns

    2 dropdowns have no label.

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 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

11 to fixGoogle 9150
  • 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.

  • Title is short (21 characters)

    Your title is only 21 characters: “www.sanjorgecc.com.mx”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

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

  • 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://www.sanjorgecc.com.mx/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at sanjorgecc.com.mx/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 3 links crawlers can't follow

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

  • No X (Twitter) card tag

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

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.

  • No llms.txt

    There is no https://www.sanjorgecc.com.mx/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 9262
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

Content and conversion

6 to fix25
  • 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 social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 7 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on sanjorgecc.com.mx, including 17 speed issues, 11 SEO issues and 6 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