Website review, no card needed

a1.mk logo

a1.mk website review

Visit site (opens in a new tab)Reviewed 30 October 202656 issues · 96 checks

This review found 56 issues worth fixing on a1.mk, 27 of them high impact, across 96 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
4.1 s3.3 sMay 9Oct 243.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.6 s
Jun 20, 20263.6 s
Jun 27, 20263.7 s
Jul 4, 20263.7 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.6 s
Aug 8, 20263.7 s
Aug 15, 20263.6 s
Aug 22, 20263.7 s
Aug 29, 20263.8 s
Sep 5, 20263.8 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20263.8 s
Oct 24, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
223 ms200 msMay 9Oct 24216 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026203 ms
May 16, 2026205 ms
May 23, 2026205 ms
May 30, 2026205 ms
Jun 6, 2026207 ms
Jun 13, 2026208 ms
Jun 20, 2026209 ms
Jun 27, 2026210 ms
Jul 4, 2026211 ms
Jul 11, 2026211 ms
Jul 18, 2026211 ms
Jul 25, 2026211 ms
Aug 1, 2026209 ms
Aug 8, 2026210 ms
Aug 15, 2026211 ms
Aug 22, 2026213 ms
Aug 29, 2026215 ms
Sep 5, 2026217 ms
Sep 12, 2026218 ms
Sep 19, 2026220 ms
Sep 26, 2026220 ms
Oct 3, 2026220 ms
Oct 10, 2026219 ms
Oct 17, 2026217 ms
Oct 24, 2026216 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.mk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. a1.mk at 1.3 s1.3 s
  2. a1.mk at 2.6 s2.6 s
  3. a1.mk at 4.0 s4.0 s
  4. a1.mk at 5.3 s5.3 s
  5. a1.mk at 6.6 s6.6 s
  6. a1.mk at 7.9 s7.9 s
  7. a1.mk at 9.2 s9.2 s
  8. a1.mk at 10.5 s10.5 s

Speed

14 to fix14
  • Improve image delivery

    5.5 s · 5.5 MB

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

  • Render-blocking requests

    7.2 s

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

  • Use efficient cache lifetimes

    5.0 s · 1.4 MB

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

  • Reduce unused JavaScript

    2.7 s · 473 KiB

    About 473 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Font display

    1.7 s

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

  • Reduce unused CSS

    1.2 s · 189 KiB

    About 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 14

    14/100

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

  • Main-thread work: 4.4 s

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Optanon and Clarity and others), adding 1.2 MB and 802 ms of main-thread time.

  • Minify JavaScript

    650 ms · 95 KiB

    95 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 452 ms

    452 ms

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

  • 13 long tasks on the main thread

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

  • 2,094 HTML elements

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

  • iwmndev.com adds 0 ms

    0 ms

    iwmndev.com costs a phone 0 ms of main-thread work and 452 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

    19 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • 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: 240 ms

    240 ms

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

Core Web Vitals

11 to fix0
  • 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.56

    0.56

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

  • Largest Contentful Paint: 38.7 s

    38.7 s

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

  • Time to Interactive: 70.8 s

    70.8 s

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

  • First Contentful Paint: 7.5 s

    7.5 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Cumulative Layout Shift: 0.657

    0.657

    The layout shifts by 0.657 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 753 ms

    753 ms

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 202 ms

    202 ms

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

  • 15 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

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

    +12%

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

2 checks passed
  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 476 ms

    476 ms

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

Images and page weight

4 to fix35
  • Page weight: 17.3 MB in 167 requests

    17.3 MB

    Your homepage downloads 17.3 MB in 167 requests on a phone: images 14.9 MB (90), scripts 1.3 MB (40) and fonts 820 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 4.6 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (11.0 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.

  • 2 images far larger than shown

    384 KiB

    2 images are downloaded at several times the size a phone draws them, for example A1_Renewal-02.png at 2,000 px wide, shown at 30 px. Resized copies would save about 384 KiB.

  • 3 images below the first screen load straight away

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

  • About 4.9 g of CO₂ per visit

    4.90 g

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

Accessibility

14 to fixGoogle 7585
  • 5 buttons without a name

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

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 13 tap targets too small

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

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 44 images without alt text

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

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Headings should not be empty (22 elements)

    Headings should not be empty: 22 elements on the page fail this check, rated minor by axe-core.

  • 11 form fields without a label

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

  • 9 links without text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • No structured data

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

  • 6 H1 headlines

    There are 6 <h1> headlines (“Navigation”, “” and “”). One clear main headline is easier for people and search engines.

  • 295 internal links, 17 external

    The homepage links to 295 pages on a1.mk and 17 external pages.

6 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “А1 Македонија е член на Групацијата А1 Телеком Австрија, водечки провајдер за комуникациски и дигитални решенија во Цен…”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “А1 Македонија - Секој твој свет - A1”.

  • Canonical URL set

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

  • 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.a1.mk: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.mk/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 (554 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 9 pages without a meta description

    https://www.a1.mk/eco-rating, https://www.a1.mk/a1-combo, https://www.a1.mk/optika, https://www.a1.mk/osiguruvanje, https://www.a1.mk/xplore-tv and https://www.a1.mk/road-assistance and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.a1.mk/netflix2, whose canonical is https://www.a1.mk/netflix. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.a1.mk/webshop/mk/categories 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 159 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

4 to fixGoogle 8174
  • 1 broken image

    1 image failed to load on a phone, for example https://www.a1.mk/.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error: Load timeout for modules: clay-tooltip/src/ClayTooltip”.

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

  • 2 distorted images

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    89 of 104 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 257 words of visible text.

3 checks passed
  • 5 short forms

    5 short forms (7 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

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

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Internet Service Provider

Company

Founded
2015
Headquarters
Skopje

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

Go beyond the website

What your $25 Growth Playbook adds

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