hops.hr website review

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

About 1.5 MB 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.

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

1 image could be 397 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.

Google CDN costs a phone 1.0 s of main-thread work and 1.8 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.

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

3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 2.0 MB and 1.1 s of main-thread time.

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

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

100 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 KiB could be saved by minifying CSS.

Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Neovisni operator prijenosnog sustava u Republici Hrvatskoj”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 17.4 MB in 69 requests on a phone: images 13.2 MB (19), scripts 2.7 MB (27) and other files 699 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

1 image (2.8 MB) 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.

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

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

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

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

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

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

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.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 4 characters: “HOPS”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://hops.hr/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at hops.hr/robots.txt, the first file search crawlers ask for.

3 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 49 pages on hops.hr and 2 external pages.

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.

There is no /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.

/ and /en/Localization/Language all use the title “HOPS”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/en/Localization/Language, /o-nama, /hrvatski-prijenosni-sustav, /koristenje-mreze-prijenos, /trziste-el-energije and /dokumenti and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

10 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link from your homepage to your own site is broken, for example https://hops.hr/en/Localization/Language (404).

http://hops.hr does not redirect to https, so some visitors land on the insecure version.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

hops.hr has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 372 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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.

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