Website review, no card needed

anker-latam.com logo

anker-latam.com website review

Visit site (opens in a new tab)Reviewed 22 October 202645 issues · 84 checks

This review found 45 issues worth fixing on anker-latam.com, 20 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
2.1 s1.3 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.6 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.6 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
169 ms143 msMay 2Oct 17157 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026159 ms
May 9, 2026155 ms
May 16, 2026166 ms
May 23, 2026164 ms
May 30, 2026156 ms
Jun 6, 2026162 ms
Jun 13, 2026152 ms
Jun 20, 2026152 ms
Jun 27, 2026151 ms
Jul 4, 2026146 ms
Jul 11, 2026148 ms
Jul 18, 2026149 ms
Jul 25, 2026148 ms
Aug 1, 2026146 ms
Aug 8, 2026150 ms
Aug 15, 2026148 ms
Aug 22, 2026151 ms
Aug 29, 2026153 ms
Sep 5, 2026152 ms
Sep 12, 2026149 ms
Sep 19, 2026149 ms
Sep 26, 2026148 ms
Oct 3, 2026152 ms
Oct 10, 2026154 ms
Oct 17, 2026157 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 anker-latam.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. anker-latam.com at 1.6 s1.6 s
  2. anker-latam.com at 3.2 s3.2 s
  3. anker-latam.com at 4.8 s4.8 s
  4. anker-latam.com at 6.5 s6.5 s
  5. anker-latam.com at 8.1 s8.1 s
  6. anker-latam.com at 9.7 s9.7 s
  7. anker-latam.com at 11.3 s11.3 s
  8. anker-latam.com at 12.9 s12.9 s

Speed

11 to fix47
  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    450 ms · 2.4 MB

    24 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused JavaScript

    1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 4.7 MB and 378 ms of main-thread time.

  • Reduce unused CSS

    450 ms · 135 KiB

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

  • 7 long tasks on the main thread

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

  • Shopify adds 0 ms

    0 ms

    Shopify costs a phone 0 ms of main-thread work and 3.2 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.

  • Google Tag Manager adds 234 ms

    234 ms

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

  • Main-thread work: 2.5 s

    A phone's processor spends 2.5 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google CDN adds 135 ms

    135 ms

    Google CDN costs a phone 135 ms of main-thread work and 733 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.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • Forced reflow

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

  • Use efficient cache lifetimes

    1 KiB

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

1 checks passed
  • Server response: 55 ms

    55 ms

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

Core Web Vitals

10 to fix67
  • 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 TTFB: 2.4 s

    2.4 s

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

  • Speed Index: 19.4 s

    19.4 s

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

  • Time to Interactive: 23.2 s

    23.2 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.7 s).

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Total Blocking Time: 594 ms

    594 ms

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

  • 9 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

3 checks passed
  • Real-user INP: 172 ms

    172 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix42
  • Page weight: 5.8 MB in 72 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 72 requests on a phone: images 2.9 MB (30), scripts 2.2 MB (20) and fonts 285 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    902 KiB

    7 images are downloaded at several times the size a phone draws them, for example Anker_DTC_homeEvent_MRC_A1654011_A1289011_A1695H11_B26971Z1_ at 3,368 px wide, shown at 342 px. Resized copies would save about 902 KiB.

  • An image on the first screen is lazy-loaded

    Anker_DTC_Home_Bannner_MRC_A1654011_A1289011_A1695H11_B26971 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.6 g of CO₂ per visit

    1.64 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8085
  • 6 buttons without a name

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

  • Interactive controls must not be nested (10 elements)

    Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

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

  • <html> element must have a valid value for the lang attribute (1 element)

    <html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 22 images without alt text

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

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

    All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.

  • 21 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 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

4 to fixGoogle 8584
  • Title is long (96 characters)

    Your title is 96 characters, so Google will cut it off around 60: “Anker, Anker Solix, Soundcore, Eufy | Tienda Oficial en México, Brasil, Chile y más paíse…”.

  • Canonical points to another host

    Your canonical URL points to ankernordics.com, not anker-latam.com, so Google may credit that host instead.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 65 internal links, 7 external

    The homepage links to 65 pages on anker-latam.com and 7 external pages.

5 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “Discover Anker and shop chargers, batteries, hubs, docks, portable power stations, conferencing gear, and more.”.

  • One H1 headline

    Your main headline reads: “Sitio oficial de Anker, Anker SOLIX, Eufy, soundcore y Nebula en los países nórdicos”.

  • Structured data in place

    Structured data found: Corporation.

  • 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.anker-latam.com/sitemap.xml.

AI search readiness

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

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (451 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.anker-latam.com/ankersolix has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.anker-latam.com/ankersolix has 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 47 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://cdn.shopify.com/s/files/1/0711/1881/5400/files/Frame_2121235014-Photoroom_1.png?v=1760084475.

  • 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 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    43 of 45 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 693 words of copy

    The homepage carries about 693 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 anker-latam.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
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Netlify

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 anker-latam.com, including 21 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

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