Website review, no card needed
fontgas.com website review
Visit site (opens in a new tab)Reviewed 25 October 202644 issues · 88 checks
This review found 44 issues worth fixing on fontgas.com, 18 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.4 s |
| May 16, 2026 | 3.5 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 115 ms |
| May 9, 2026 | 115 ms |
| May 16, 2026 | 115 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 107 ms |
| Jun 6, 2026 | 106 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 114 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 117 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 114 ms |
| Aug 22, 2026 | 111 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 109 ms |
| Sep 19, 2026 | 111 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 106 ms |
| Oct 17, 2026 | 105 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
How it loaded on a phone
0.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Use efficient cache lifetimes
5.5 s · 8.1 MB309 files are served with short cache lifetimes, so returning visitors download them again (8.1 MB).
Improve image delivery
1.4 s · 6.0 MB181 images could be 6.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
4.7 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Reduce unused CSS
1.8 s · 360 KiBAbout 360 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 22
22/100Your mobile performance score is 22 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.2 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 CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.4 MB and 1.3 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 977 ms. During a long task the page ignores taps.
Google CDN adds 698 ms
698 msGoogle CDN costs a phone 698 ms of main-thread work and 734 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
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Google Tag Manager adds 519 ms
519 msGoogle Tag Manager costs a phone 519 ms of main-thread work and 349 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.
Reduce unused JavaScript
534 KiBAbout 534 KiB of JavaScript is downloaded but never used on this page.
1,875 HTML elements
The page has 1,875 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Phones get a much slower page than desktops
Desktop scores 70 but mobile only 22. A gap that wide usually means heavy scripts and images that hit phones hardest.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
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: 6 ms
6 msYour server sent the HTML in 6 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.
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Visita nuestras tiendas Fontgas y llévate el material que n…”.
Speed Index: 12.4 s
12.4 sVisually, the page fills in at 12.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.8 s
4.8 sThe first text or image appears after 4.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.196
0.196The layout shifts by 0.196 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 105 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-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 96 ms
96 msReal visitors wait 96 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 577 ms
577 msReal visitors wait 577 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 9.8 MB in 344 requests
9.8 MBYour homepage downloads 9.8 MB in 344 requests on a phone: images 7.3 MB (224), scripts 1.4 MB (89) and stylesheets 400 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
tres-new.png weighs 2.9 MB. On a phone connection a single image that size takes seconds.
37 images below the first screen load straight away
37 images further down the page (3.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (3.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.
About 2.8 g of CO₂ per visit
2.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.77 g of CO₂e: 332.7 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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (2 elements)
Headings should not be empty: 2 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.
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 222 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.
85 internal links, 19 external
The homepage links to 85 pages on fontgas.com and 19 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Proveedor de soluciones y suministros técnicos en fontanería, climatización, electricidad, iluminación, baño y riego. D…”.
Title: 63 characters
Your title is a healthy 63 characters: “Proveedor de fontanería, climatización y electricidad | Fontgas”.
Canonical URL set
The canonical URL is https://www.fontgas.com/.
Structured data in place
Structured data found: WebPage.
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.fontgas.com/sitemap_index.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (873 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fontgas.com/llms.txt (3 KiB, 26 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://www.fontgas.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.fontgas.com/blog took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 12 pages that loaded have a meta description.
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
10 small tap targets
10 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.15.4/css/all.css?ver=2.0.3' from origin 'https://w…”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
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.
Thin social proof
Social proof on the homepage: 27 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.
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 400 words of copy
The homepage carries about 400 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before 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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
10 other companies contacted
Loading the homepage contacts 10 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 fontgas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on fontgas.com, including 22 speed issues, 1 SEO issue and 4 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.