Website review, no card needed
siigo.com website review
Visit site (opens in a new tab)Reviewed 20 November 202643 issues · 93 checks
This review found 43 issues worth fixing on siigo.com, 13 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.1 s |
| Nov 7, 2026 | 3.0 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 318 ms |
| Jun 6, 2026 | 320 ms |
| Jun 13, 2026 | 318 ms |
| Jun 20, 2026 | 322 ms |
| Jun 27, 2026 | 332 ms |
| Jul 4, 2026 | 345 ms |
| Jul 11, 2026 | 358 ms |
| Jul 18, 2026 | 363 ms |
| Jul 25, 2026 | 362 ms |
| Aug 1, 2026 | 359 ms |
| Aug 8, 2026 | 357 ms |
| Aug 15, 2026 | 359 ms |
| Aug 22, 2026 | 361 ms |
| Aug 29, 2026 | 361 ms |
| Sep 5, 2026 | 360 ms |
| Sep 12, 2026 | 349 ms |
| Sep 19, 2026 | 342 ms |
| Sep 26, 2026 | 339 ms |
| Oct 3, 2026 | 329 ms |
| Oct 10, 2026 | 330 ms |
| Oct 17, 2026 | 340 ms |
| Oct 24, 2026 | 341 ms |
| Oct 31, 2026 | 342 ms |
| Nov 7, 2026 | 343 ms |
| Nov 14, 2026 | 344 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
Speed
Reduce unused JavaScript
7.0 s · 2.5 MBAbout 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.0 s faster on a phone.
Reduce unused CSS
1.2 s · 211 KiBAbout 211 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.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.2 s
A phone's processor spends 8.2 s on main-thread work while loading, 5.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.5 MB and 2.2 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.
Use efficient cache lifetimes
650 ms · 665 KiB25 files are served with short cache lifetimes, so returning visitors download them again (665 KiB).
Google Tag Manager adds 845 ms
845 msGoogle Tag Manager costs a phone 845 ms of main-thread work and 1.0 MB 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.
Render-blocking requests
850 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Google CDN adds 433 ms
433 msGoogle CDN costs a phone 433 ms of main-thread work and 745 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.
Facebook adds 266 ms
266 msFacebook costs a phone 266 ms of main-thread work and 267 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.
1,615 HTML elements
The page has 1,615 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
250 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Improve image delivery
150 ms · 87 KiB3 images could be 87 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
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 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 24.3 s
24.3 sYour largest element takes 24.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 45.1 s
45.1 sThe page becomes fully interactive after 45.1 s. Good is under 3.8 s.
Total Blocking Time: 3.0 s
3.0 sScripts block taps and scrolling for 3.0 s in total while the page loads. Good is under 200 ms.
Speed Index: 11.3 s
11.3 sVisually, the page fills in at 11.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 361 ms
361 msReal visitors wait 361 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 802 ms
802 msReal visitors wait 802 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 318 ms to 344 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 148 requests
7.4 MBYour homepage downloads 7.4 MB in 148 requests on a phone: scripts 5.2 MB (62), fonts 1.3 MB (11) and other files 381 KiB (49). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 252.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
22 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 25 WCAG 2.2 A/AA and best-practice rules on the phone render: 22 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
107 internal links, 41 external
The homepage links to 107 pages on siigo.com and 41 external pages.
8 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Compra tu software contable y administrativo 100% online con hasta 30% de descuento. Oferta válida solo en Noviembre. ¡…”.
One H1 headline
Your main headline reads: “Siigo, sistema administrativo y contable 100% en la nube”.
Title: 57 characters
Your title is a healthy 57 characters: “Siigo Colombia | Ecomm Mes - Beneficios Exclusivos Online”.
Canonical URL set
The canonical URL is https://www.siigo.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, LocalBusiness and Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://www.siigo.com/sitemap.xml.
AI search readiness
3 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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
llms.txt published
The site publishes https://www.siigo.com/llms.txt (3 KiB, 23 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.siigo.com/facturacion-electronica-whatsapp is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
https://www.siigo.com/prueba-gratis, https://www.siigo.com/contactenos and https://www.siigo.com/blog all use the title “Siigo | Software Contable y Administrativo, Ideal para Pymes”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://www.siigo.com/prueba-gratis, https://www.siigo.com/contactenos, https://www.siigo.com/blog and https://www.siigo.com/facturacion-electronica-whatsapp use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.siigo.com/peru, whose canonical is https://www.siigo.com/pe. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages slow to respond
https://www.siigo.com/contactenos and https://www.siigo.com/eventos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187114504&tm=gtm002&Ver=2&mid=eebdd859-dd48-4aa9-b04a-e59cdb236f7f&bo=1&sid=9a191440e4ce11f19fabeb26f7c6785b&vid=9a193d70e4ce11f1926c99e81183422f&vids=1&msclkid=N&pi=9.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive 'object-src' contains the keyword 'none' alongside with other source expressions.…”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 26 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 17 words
The homepage has only about 17 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
4 checks passed
1 short form
A short form (4 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Cloudflare Web Analytics.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 3 mores (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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 2 of them by other companies (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.
33 other companies contacted
Loading the homepage contacts 33 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 siigo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Azure
Company
- Headquarters
- Bogota
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on siigo.com, including 20 speed 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.