Hzzo.hr Site Title
Naslovna | Hrvatski zavod za zdravstveno osiguranje
Hzzo.hr Test Results
Hzzo.hr Mobile Performance: 74/100
Quick overview:
Max Potential First Input Delay
220 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
3.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
4.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Resources Summary
Aggregates all network requests and groups them by type
Diagnostics
Collection of useful page vitals.
Network Round Trip Times
40 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Script Treemap Data
Used for treemap app
Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Network Requests
Lists the network requests that were made during page load.
Server Backend Latencies
30 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Final Screenshot
The last screenshot captured of the pageload.
77719074446
Hzzo.hr Mobile SEO: 93/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Hzzo.hr Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Hzzo.hr Mobile PWA: 75/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more about splash screens. Failures: Manifest does not have `name`.
Hzzo.hr Mobile Accessibility: 68/100
Quick overview:
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
`[role]`s are not contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.hzzo.com
www.hzzo.net
www.hzzo.org
www.hzzo.info
www.hzzo.biz
www.hzzo.us
www.hzzo.mobi
www.zzo.hr
www.hzzo.hr
www.bzzo.hr
www.hbzzo.hr
www.bhzzo.hr
www.gzzo.hr
www.hgzzo.hr
www.ghzzo.hr
www.yzzo.hr
www.hyzzo.hr
www.yhzzo.hr
www.uzzo.hr
www.huzzo.hr
www.uhzzo.hr
www.jzzo.hr
www.hjzzo.hr
www.jhzzo.hr
www.nzzo.hr
www.hnzzo.hr
www.nhzzo.hr
www.hzo.hr
www.hxzo.hr
www.hzxzo.hr
www.hxzzo.hr
www.hszo.hr
www.hzszo.hr
www.hszzo.hr
www.hazo.hr
www.hzazo.hr
www.hazzo.hr
www.hzxo.hr
www.hzzxo.hr
www.hzso.hr
www.hzzso.hr
www.hzao.hr
www.hzzao.hr
www.hzz.hr
www.hzzi.hr
www.hzzoi.hr
www.hzzio.hr
www.hzzk.hr
www.hzzok.hr
www.hzzko.hr
www.hzzl.hr
www.hzzol.hr
www.hzzlo.hr
www.hzzp.hr
www.hzzop.hr
www.hzzpo.hr
www.hzzo.net
www.hzzo.org
www.hzzo.info
www.hzzo.biz
www.hzzo.us
www.hzzo.mobi
www.zzo.hr
www.hzzo.hr
www.bzzo.hr
www.hbzzo.hr
www.bhzzo.hr
www.gzzo.hr
www.hgzzo.hr
www.ghzzo.hr
www.yzzo.hr
www.hyzzo.hr
www.yhzzo.hr
www.uzzo.hr
www.huzzo.hr
www.uhzzo.hr
www.jzzo.hr
www.hjzzo.hr
www.jhzzo.hr
www.nzzo.hr
www.hnzzo.hr
www.nhzzo.hr
www.hzo.hr
www.hxzo.hr
www.hzxzo.hr
www.hxzzo.hr
www.hszo.hr
www.hzszo.hr
www.hszzo.hr
www.hazo.hr
www.hzazo.hr
www.hazzo.hr
www.hzxo.hr
www.hzzxo.hr
www.hzso.hr
www.hzzso.hr
www.hzao.hr
www.hzzao.hr
www.hzz.hr
www.hzzi.hr
www.hzzoi.hr
www.hzzio.hr
www.hzzk.hr
www.hzzok.hr
www.hzzko.hr
www.hzzl.hr
www.hzzol.hr
www.hzzlo.hr
www.hzzp.hr
www.hzzop.hr
www.hzzpo.hr