Website review, no card needed
lipigas.cl website review
Visit site (opens in a new tab)Reviewed 27 October 202648 issues · 90 checks
This review found 48 issues worth fixing on lipigas.cl, 20 of them high impact, across 90 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.9 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 271 ms |
| May 16, 2026 | 279 ms |
| May 23, 2026 | 290 ms |
| May 30, 2026 | 304 ms |
| Jun 6, 2026 | 313 ms |
| Jun 13, 2026 | 312 ms |
| Jun 20, 2026 | 305 ms |
| Jun 27, 2026 | 302 ms |
| Jul 4, 2026 | 301 ms |
| Jul 11, 2026 | 304 ms |
| Jul 18, 2026 | 314 ms |
| Jul 25, 2026 | 329 ms |
| Aug 1, 2026 | 350 ms |
| Aug 8, 2026 | 371 ms |
| Aug 15, 2026 | 380 ms |
| Aug 22, 2026 | 378 ms |
| Aug 29, 2026 | 371 ms |
| Sep 5, 2026 | 362 ms |
| Sep 12, 2026 | 364 ms |
| Sep 19, 2026 | 375 ms |
| Sep 26, 2026 | 386 ms |
| Oct 3, 2026 | 401 ms |
| Oct 10, 2026 | 407 ms |
| Oct 17, 2026 | 408 ms |
| Oct 24, 2026 | 414 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
11.7 s · 5.5 MBAbout 5.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.7 s faster on a phone.
Use efficient cache lifetimes
3.8 s · 857 KiB47 files are served with short cache lifetimes, so returning visitors download them again (857 KiB).
Render-blocking requests
2.8 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Google Tag Manager adds 2.3 s
2.3 sGoogle Tag Manager costs a phone 2.3 s of main-thread work and 3.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.7 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 6.2 MB and 3.9 s of main-thread time.
Google CDN adds 882 ms
882 msGoogle CDN costs a phone 882 ms of main-thread work and 2.1 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.
Reduce unused CSS
450 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify CSS
300 ms · 11 KiB11 KiB could be saved by minifying CSS.
Facebook adds 278 ms
278 msFacebook costs a phone 278 ms of main-thread work and 309 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 255 ms. During a long task the page ignores taps.
Google Maps adds 118 ms
118 msGoogle Maps costs a phone 118 ms of main-thread work and 392 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Legacy JavaScript
150 ms · 23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
99 KiB7 images could be 99 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
10 KiB10 KiB could be saved by minifying JavaScript.
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: 25 ms
25 msYour server sent the HTML in 25 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.
Real-user CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
First Contentful Paint: 11.2 s
11.2 sThe first text or image appears after 11.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 28.3 s
28.3 sYour largest element takes 28.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nuestro nuevo reconocimiento lleva el nombre de nuestros cl…”.
Time to Interactive: 50.2 s
50.2 sThe page becomes fully interactive after 50.2 s. Good is under 3.8 s.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.1 s
2.1 sScripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 490 ms
490 msReal visitors wait 490 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 49% slower for real visitors
+49%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 271 ms to 414 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
40 images without width and height
40 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.4 MB in 234 requests
9.4 MBYour homepage downloads 9.4 MB in 234 requests on a phone: scripts 6.6 MB (93), other files 1.1 MB (44) and images 870 KiB (57). Under 2 MB keeps phones on slow connections fast.
4 images in older formats
4 images (279 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (106 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.67 g of CO₂e: 320.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 text elements with low contrast
3 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 (41 elements)
All page content should be contained by landmarks: 41 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.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
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 46 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (7 characters)
Your title is only 7 characters: “Lipigas”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (222 characters)
Your meta description is 222 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
143 internal links, 33 external
The homepage links to 143 pages on lipigas.cl and 33 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://lipigas.cl/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://lipigas.cl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://lipigas.cl/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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,071 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page points its canonical at the homepage
https://lipigas.cl/negocios declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://lipigas.cl/negocios all use the title “Lipigas”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://lipigas.cl/lipibolsas has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://lipigas.cl/negocios has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://lipigas.cl/negocios took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of undefined (reading 'addEventListener')”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
23 of 24 tappable elements near the top are at least 24 px.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 602 words of copy
The homepage carries about 602 words of visible text.
3 checks passed
12 short forms
12 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
29 other companies contacted
Loading the homepage contacts 29 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 lipigas.cl, 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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on lipigas.cl, including 26 speed issues, 4 SEO issues and 3 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.