Website review, no card needed

a1.hr logo

a1.hr website review

Visit site (opens in a new tab)Reviewed 18 November 202649 issues · 92 checks

This review found 49 issues worth fixing on a1.hr, 18 of them high impact, across 92 checks. The most urgent: reduce unused JavaScript. 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
4.0 s3.4 sMay 30Nov 143.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.7 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20263.8 s
Jul 4, 20263.8 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.6 s
Sep 12, 20263.5 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.6 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.5 s
Nov 7, 20263.5 s
Nov 14, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
263 ms211 msMay 30Nov 14217 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026244 ms
Jun 6, 2026247 ms
Jun 13, 2026251 ms
Jun 20, 2026253 ms
Jun 27, 2026254 ms
Jul 4, 2026255 ms
Jul 11, 2026252 ms
Jul 18, 2026253 ms
Jul 25, 2026253 ms
Aug 1, 2026252 ms
Aug 8, 2026254 ms
Aug 15, 2026255 ms
Aug 22, 2026257 ms
Aug 29, 2026254 ms
Sep 5, 2026250 ms
Sep 12, 2026240 ms
Sep 19, 2026230 ms
Sep 26, 2026226 ms
Oct 3, 2026223 ms
Oct 10, 2026224 ms
Oct 17, 2026226 ms
Oct 24, 2026226 ms
Oct 31, 2026222 ms
Nov 7, 2026219 ms
Nov 14, 2026217 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 a1.hr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. a1.hr at 2.6 s2.6 s
  2. a1.hr at 5.2 s5.2 s
  3. a1.hr at 7.8 s7.8 s
  4. a1.hr at 10.4 s10.4 s
  5. a1.hr at 13.0 s13.0 s
  6. a1.hr at 15.6 s15.6 s
  7. a1.hr at 18.2 s18.2 s
  8. a1.hr at 20.8 s20.8 s

Speed

15 to fix26
  • Reduce unused JavaScript

    2.0 s · 4.3 MB

    About 4.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Reduce unused CSS

    1.8 s · 458 KiB

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

  • Main-thread work: 17.9 s

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

  • YouTube adds 1.3 s

    1.3 s

    YouTube costs a phone 1.3 s of main-thread work and 2.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.

  • Google CDN adds 1.1 s

    1.1 s

    Google CDN costs a phone 1.1 s of main-thread work and 1.9 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: 26

    26/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google CDN and giosg.com and others), adding 6.5 MB and 4.6 s of main-thread time.

  • Improve image delivery

    350 ms · 2.2 MB

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

  • Use efficient cache lifetimes

    1.5 MB

    40 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).

  • giosg.com adds 974 ms

    974 ms

    giosg.com costs a phone 974 ms of main-thread work and 1.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.

  • 20 long tasks on the main thread

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

  • infobip.com adds 521 ms

    521 ms

    infobip.com costs a phone 521 ms of main-thread work and 647 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.

  • Minify JavaScript

    410 ms · 174 KiB

    174 KiB could be saved by minifying JavaScript.

  • 2,669 HTML elements

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

  • Minify CSS

    110 ms · 18 KiB

    18 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    93 KiB

    Polyfills for old browsers add 93 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: 259 ms

    259 ms

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

Core Web Vitals

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

  • Speed Index: 23.0 s

    23.0 s

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

  • Total Blocking Time: 5.0 s

    5.0 s

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

  • Time to Interactive: 69.8 s

    69.8 s

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

  • Largest Contentful Paint: 8.3 s

    8.3 s

    Your largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “black friday popusti do 90%”.

  • First Contentful Paint: 6.1 s

    6.1 s

    The first text or image appears after 6.1 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: 207 ms

    207 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Real-user TTFB: 658 ms

    658 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

2 to fix60
  • Page weight: 13.8 MB in 315 requests

    13.8 MB

    Your homepage downloads 13.8 MB in 315 requests on a phone: scripts 8.3 MB (111), images 3.0 MB (69) and other files 1,013 KiB (81). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    34 KiB

    1 image is downloaded at several times the size a phone draws it, for example logo.png at 212 px wide, shown at 40 px. Resized copies would save about 34 KiB.

  • 1 image in older formats

    1 image (50 KiB) is 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.

  • 3 images below the first screen load straight away

    3 images further down the page (151 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.9 g of CO₂ per visit

    3.90 g

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

Accessibility

8 to fixGoogle 9791
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 images without alt text

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

  • Main landmark should not be contained in another landmark (5 elements)

    Main landmark should not be contained in another landmark: 5 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main 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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 10081
  • Title is short (19 characters)

    Your title is only 19 characters: “A1.hr | A1 Hrvatska”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Black Friday” and “Sve za tvoj dom na jednom mjestu”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 215 internal links, 30 external

    The homepage links to 215 pages on a1.hr and 30 external pages.

4 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “Najbolje cijene mobitela, super ponude tarifa, akcije, najnoviji modeli iPhone, Samsung, Huawei i ostalih brendova. Nar…”.

  • Canonical URL set

    The canonical URL is https://www.a1.hr/.

  • 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.a1.hr:443/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.a1.hr/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.

  • Text is in the HTML

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.a1.hr/privatni 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://www.a1.hr/privatni all use the title “A1.hr | A1 Hrvatska”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.a1.hr/tko-smo-mi/buducnost-na-prvom-mjestu, https://www.a1.hr/privatni/virtualni-shop and https://www.a1.hr/about-us have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.a1.hr/podrska, https://www.a1.hr/about-us and https://www.a1.hr/privatni/mobiteli/tarife-na-pretplatu have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.a1.hr/poslovni and https://www.a1.hr/boljionline took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 84 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 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5494
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    14 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 2 trust badges. 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 476 words of copy

    The homepage carries about 476 words of visible text.

3 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Virtualni shop”, “Shop za sve” and “Shop za sve NOVO”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 1 of them by other companies (measured from a US location before any click).

  • 26 other companies contacted

    Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 a1.hr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
A1 Hrvatska d.o.o.

Company

Founded
1999
Headquarters
Zagreb

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on a1.hr, including 25 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