Website review, no card needed

technomarine.co logo

technomarine.co website review

Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 84 checks

This review found 45 issues worth fixing on technomarine.co, 17 of them high impact, across 84 checks. The most urgent: improve image delivery. 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
3.1 s2.3 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
314 ms223 msMay 16Oct 31303 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026233 ms
May 23, 2026237 ms
May 30, 2026242 ms
Jun 6, 2026242 ms
Jun 13, 2026243 ms
Jun 20, 2026246 ms
Jun 27, 2026248 ms
Jul 4, 2026252 ms
Jul 11, 2026254 ms
Jul 18, 2026254 ms
Jul 25, 2026247 ms
Aug 1, 2026246 ms
Aug 8, 2026247 ms
Aug 15, 2026249 ms
Aug 22, 2026255 ms
Aug 29, 2026256 ms
Sep 5, 2026258 ms
Sep 12, 2026253 ms
Sep 19, 2026251 ms
Sep 26, 2026248 ms
Oct 3, 2026254 ms
Oct 10, 2026266 ms
Oct 17, 2026278 ms
Oct 24, 2026293 ms
Oct 31, 2026303 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 technomarine.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. technomarine.co at 0.6 s0.6 s
  2. technomarine.co at 1.2 s1.2 s
  3. technomarine.co at 1.8 s1.8 s
  4. technomarine.co at 2.4 s2.4 s
  5. technomarine.co at 2.9 s2.9 s
  6. technomarine.co at 3.5 s3.5 s
  7. technomarine.co at 4.1 s4.1 s
  8. technomarine.co at 4.7 s4.7 s

Speed

15 to fix42
  • Improve image delivery

    11.5 s · 2.9 MB

    10 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.5 s faster on a phone.

  • Render-blocking requests

    6.2 s

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

  • Use efficient cache lifetimes

    1.2 s · 397 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (397 KiB).

  • Mobile performance score: 42

    42/100

    Your mobile performance score is 42. 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.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3,307 HTML elements

    The page has 3,307 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Azure Web Services, Cloudflare CDN and Clarity and others), adding 29.9 MB and 1.8 s of main-thread time.

  • Shopify adds 120 ms

    120 ms

    Shopify costs a phone 120 ms of main-thread work and 28.4 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 JavaScript

    750 ms · 465 KiB

    About 465 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Azure Web Services adds 921 ms

    921 ms

    Azure Web Services costs a phone 921 ms of main-thread work and 178 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 CSS

    600 ms · 74 KiB

    About 74 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Minify CSS

    300 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Cloudflare CDN adds 222 ms

    222 ms

    Cloudflare CDN costs a phone 222 ms of main-thread work and 612 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.

  • 16 long tasks on the main thread

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

  • Google Tag Manager adds 187 ms

    187 ms

    Google Tag Manager costs a phone 187 ms of main-thread work and 352 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.

  • Duplicated JavaScript

    100 ms · 25 KiB

    25 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • Font display

    50 ms

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

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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: 14 ms

    14 ms

    Your server sent the HTML in 14 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.

  • Largest Contentful Paint: 38.8 s

    38.8 s

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

  • Time to Interactive: 46.7 s

    46.7 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 294 ms

    294 ms

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

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

    +27%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 575 ms

    575 ms

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

  • 3 images without width and height

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 694 ms

    694 ms

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

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

    -17%

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

  • Cumulative Layout Shift: 0.005

    0.005

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

Images and page weight

1 to fix33
  • Page weight: 40.8 MB in 315 requests

    40.8 MB

    Your homepage downloads 40.8 MB in 315 requests on a phone: media 27.4 MB (2), images 9.8 MB (63) and scripts 2.0 MB (81). Under 2 MB keeps phones on slow connections fast.

  • About 11.6 g of CO₂ per visit

    11.55 g

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

Accessibility

9 to fixGoogle 7281
  • Delayed refresh under 20 hours must not be used (1 element)

    Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

  • 7 images without alt text

    7 images have no alt text, which hurts accessibility and image search.

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

  • Definition list items are not wrapped in <dl> elements

    Definition list items are not wrapped in <dl> elements (64 elements).

  • 34 tap targets too small

    34 tap targets are too small or too close together to hit reliably with a finger.

  • <dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

    <dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. (32 elements).

  • Orphan list items

    Some list items are not inside a list.

  • 21 text elements with low contrast

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 20 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 7788
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 130 internal links, 12 external

    The homepage links to 130 pages on technomarine.co and 12 external pages.

7 checks passed
  • Meta description: 82 characters

    Your meta description is 82 characters: “Techno Hot Relojes desde 399.900. Hasta 65%Off en relojes. Relojes 100% Originales”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Technomarine Colombia | Hasta 65%off”.

  • Canonical URL set

    The canonical URL is https://technomarine.co/.

  • Structured data in place

    Structured data found: Organization 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://technomarine.co/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://technomarine.co/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.

2 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://technomarine.co/collections/eternal-elements and https://technomarine.co/collections/sea-manta have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://technomarine.co/collections/sea-manta, https://technomarine.co/collections/cruise and https://technomarine.co/collections/uf6 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 81 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

  • 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 5 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9289
  • 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 429 ()”.

  • 5 distorted images

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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.

  • Only about 10 words

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

  • 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
  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 249 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

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

  • 2 other companies contacted

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Microsoft Clarity · Smart Filter Search · Mercado Pago Antifraud Plus · Globo Mega Menu · Smart Product Filters · Mercadopago Pf App · Ctx Whatsapp Chat Marketing · hulkapps.com · pushowl.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on technomarine.co, including 26 speed issues, 2 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

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