Hdlu.hr Site Title

HRVATSKO DRUSTVO LIKOVNIH UMJETNIKA

Hdlu.hr Meta Description

Hrvatsko društvo likovnih umjetnika je nevladina, neprofitna i nestranačka strukovna udruga čiji su članovi likovni umjetnici iz svih dijelova Hrvatske.

Hdlu.hr Test Results

Hdlu.hr Mobile Performance: 26/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Potential savings of 298 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Efficiently encode images
Potential savings of 446 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce JavaScript execution time
1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Eliminate render-blocking resources
Potential savings of 1,560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Largest Contentful Paint element
6,960 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid serving legacy JavaScript to modern browsers
Potential savings of 15 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Reduce unused JavaScript
Potential savings of 146 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Minimize main-thread work
3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Defer offscreen images
Potential savings of 125 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve images in next-gen formats
Potential savings of 893 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Serve static assets with an efficient cache policy
64 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Time to Interactive
10.7 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.
Max Potential First Input Delay
250 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.

Hdlu.hr Mobile SEO: 85/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Hdlu.hr Mobile Best Practices: 72/100
Quick overview:
Trust and Safety
Does not use HTTPS
4 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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document contains a `doctype` that triggers `limited-quirks-mode`
Hdlu.hr Mobile Accessibility: 69/100
Quick overview:
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.
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.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
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.
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.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar tests
www.hdlu.com
www.hdlu.net
www.hdlu.org
www.hdlu.info
www.hdlu.biz
www.hdlu.us
www.hdlu.mobi
www.dlu.hr
www.hdlu.hr
www.bdlu.hr
www.hbdlu.hr
www.bhdlu.hr
www.gdlu.hr
www.hgdlu.hr
www.ghdlu.hr
www.ydlu.hr
www.hydlu.hr
www.yhdlu.hr
www.udlu.hr
www.hudlu.hr
www.uhdlu.hr
www.jdlu.hr
www.hjdlu.hr
www.jhdlu.hr
www.ndlu.hr
www.hndlu.hr
www.nhdlu.hr
www.hlu.hr
www.hxlu.hr
www.hdxlu.hr
www.hxdlu.hr
www.hslu.hr
www.hdslu.hr
www.hsdlu.hr
www.helu.hr
www.hdelu.hr
www.hedlu.hr
www.hrlu.hr
www.hdrlu.hr
www.hrdlu.hr
www.hflu.hr
www.hdflu.hr
www.hfdlu.hr
www.hclu.hr
www.hdclu.hr
www.hcdlu.hr
www.hdu.hr
www.hdpu.hr
www.hdlpu.hr
www.hdplu.hr
www.hdou.hr
www.hdlou.hr
www.hdolu.hr
www.hdku.hr
www.hdlku.hr
www.hdklu.hr
www.hdl.hr
www.hdly.hr
www.hdluy.hr
www.hdlyu.hr
www.hdlh.hr
www.hdluh.hr
www.hdlhu.hr
www.hdlj.hr
www.hdluj.hr
www.hdlju.hr
www.hdli.hr
www.hdlui.hr
www.hdliu.hr
Last Tested: