Website review, no card needed

synergias.org logo

synergias.org website review

Visit site (opens in a new tab)Reviewed 9 November 202646 issues · 79 checks

This review found 46 issues worth fixing on synergias.org, 15 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of synergias.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. synergias.org at 0.5 s0.5 s
  2. synergias.org at 0.9 s0.9 s
  3. synergias.org at 1.4 s1.4 s
  4. synergias.org at 1.9 s1.9 s
  5. synergias.org at 2.3 s2.3 s
  6. synergias.org at 2.8 s2.8 s
  7. synergias.org at 3.3 s3.3 s
  8. synergias.org at 3.7 s3.7 s

Speed

7 to fix64
  • Use efficient cache lifetimes

    3.0 s · 6.9 MB

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

  • Render-blocking requests

    3.0 s

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

  • Reduce unused CSS

    1.2 s · 191 KiB

    About 191 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Improve image delivery

    4.7 MB

    10 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 64

    64/100

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

  • Reduce unused JavaScript

    450 ms · 83 KiB

    About 83 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.

  • Font display

    350 ms

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

  • 1 long task on the main thread

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

  • Document request latency

    36 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify CSS

    11 KiB

    11 KiB could be saved by minifying CSS.

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

  • Forced reflow

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Google Fonts), adding 2 KiB and 0 ms of main-thread time.

2 checks passed
  • Main-thread work: 0.4 s

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

  • Server response: 107 ms

    107 ms

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

Core Web Vitals

5 to fix71
  • Largest Contentful Paint: 6.1 s

    6.1 s

    Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Descubre el poder de la colaboración con nuestra plataforma…”. Most of its time is element render delay (2.9 s).

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • 24 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 6 ms

    6 ms

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

Images and page weight

5 to fix18
  • Page weight: 6.9 MB in 36 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 36 requests on a phone: images 6.4 MB (20), stylesheets 232 KiB (8) and scripts 212 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    EuxgdKokU5ROwi1HXpA2vTGjILnPZDz8.jpg weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.3 MB

    3 images are downloaded at several times the size a phone draws them, for example EuxgdKokU5ROwi1HXpA2vTGjILnPZDz8.jpg at 2,000 px wide, shown at 342 px. Resized copies would save about 1.3 MB.

  • 5 images in older formats

    5 images (2.1 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 (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.96 g

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

Accessibility

7 to fixGoogle 8290
  • 9 buttons without a name

    9 buttons have no accessible name, so screen readers announce just “button”.

  • 26 text elements with low contrast

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

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

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

  • 3 links without text

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

  • ARIA role should be appropriate for the element (4 elements)

    ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (4 elements)

    Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

7 to fixGoogle 10068
  • Title is short (13 characters)

    Your title is only 13 characters: “Synergias.org”. 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.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Transforma tu red de contactos en ingresos”, “Haz crecer tu negocio” and “Dominando Nuevos Nichos: Liderazgo en Mercados Em…”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • Meta description is long (327 characters)

    Your meta description is 327 characters; Google truncates after about 160, so the end of your pitch is cut.

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

    There is no robots.txt at synergias.org/robots.txt, the first file search crawlers ask for.

  • No X (Twitter) card tag

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

  • 16 internal links, 0 external

    The homepage links to 16 pages on synergias.org and 0 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://synergias.org/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    56%

    The HTML your server sends has 1,677 of the 2,975 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

Other pages

6 to fix43
  • 1 linked page is broken

    Your homepage links to https://synergias.org/contact, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://synergias.org/AuthController/change_language/2 has no <title>, so Google invents the link text in results.

  • 3 pages share a title

    /, https://synergias.org/faq and https://synergias.org/terms-of-use all use the title “Synergias.org”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://synergias.org/store and https://synergias.org/AuthController/change_language/2 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://synergias.org/faq and https://synergias.org/terms-of-use use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://synergias.org/terms-of-use and https://synergias.org/AuthController/change_language/2 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9291
  • 4 small tap targets

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

  • 7 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • Thin social proof

    Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • 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 2,975 words of copy

    The homepage carries about 2,975 words of visible text.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 1 other company contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
OVHcloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on synergias.org, including 12 speed issues, 7 SEO issues and 5 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