Tools & Wizards About Us
hallein.at screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

hallein.at

Hallein - Stadtgemeinde - Startseite

Page Load Speed

5.8 sec in total

First Response

432 ms

Resources Loaded

4.2 sec

Page Rendered

1.2 sec

hallein.at screenshot

About Website

Welcome to hallein.at homepage info - get ready to check Hallein best content for Austria right away, or after learning these important things about hallein.at

Hallein

Visit hallein.at

Key Findings

We analyzed Hallein.at page load time and found that the first response time was 432 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

hallein.at performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

hallein.at

432 ms

hallein.gv.at

486 ms

www.hallein.gv.at

820 ms

getdocument.ashx

91 ms

riscms_pre.css

179 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hallein.at, 88% (70 requests) were made to Hallein.gv.at and 11% (9 requests) were made to Cdnfile.gem2go.page. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Hallein.gv.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 533.4 kB (12%)

Content Size

4.4 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hallein.at main page is 4.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 162.3 kB

  • Original 183.5 kB
  • After minification 128.3 kB
  • After compression 21.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 55.3 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 162.3 kB or 88% of the original size.

Image Optimization

-9%

Potential reduce by 335.5 kB

  • Original 3.8 MB
  • After minification 3.5 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Hallein images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 26.8 kB

  • Original 216.7 kB
  • After minification 216.7 kB
  • After compression 189.9 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 26.8 kB or 12% of the original size.

CSS Optimization

-6%

Potential reduce by 8.8 kB

  • Original 149.4 kB
  • After minification 149.4 kB
  • After compression 140.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Hallein.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (60%)

Requests Now

65

After Optimization

26

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hallein. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hallein.at

hallein.at

432 ms

hallein.gv.at

hallein.gv.at

486 ms

www.hallein.gv.at

www.hallein.gv.at

820 ms

getdocument.ashx

getdocument.ashx

91 ms

riscms_pre.css

riscms_pre.css

179 ms

jquery-ui-1.8.17.min.css

jquery-ui-1.8.17.min.css

271 ms

video_overlay.css

video_overlay.css

299 ms

main.css

main.css

288 ms

bootstrap.min.css

bootstrap.min.css

358 ms

slick.min.css

slick.min.css

379 ms

slick-theme.min.css

slick-theme.min.css

392 ms

slick-ris.min.css

slick-ris.min.css

383 ms

slick-ris-indiv.min.css

slick-ris-indiv.min.css

388 ms

2061.css

2061.css

445 ms

all.min.css

all.min.css

649 ms

jquery.min_1.7.2.js

jquery.min_1.7.2.js

556 ms

video_overlay.js

video_overlay.js

471 ms

AdapterUtils.js

AdapterUtils.js

478 ms

jquery-ui-1.8.17.min.js

jquery-ui-1.8.17.min.js

721 ms

jquery.validate.js

jquery.validate.js

533 ms

jquery.lazy.min.js

jquery.lazy.min.js

588 ms

jquery.lazy.plugins.min.js

jquery.lazy.plugins.min.js

565 ms

MenuAdapter.js

MenuAdapter.js

618 ms

mobileMenu.js

mobileMenu.js

697 ms

tagcloud.js

tagcloud.js

690 ms

template.js

template.js

699 ms

slick.min.js

slick.min.js

704 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

742 ms

rismap3leaflet.js

rismap3leaflet.js

748 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

787 ms

jquery.socialshareprivacy.js

jquery.socialshareprivacy.js

789 ms

getdocument.ashx

getdocument.ashx

833 ms

splide.min.css

splide.min.css

397 ms

splide.min.js

splide.min.js

403 ms

iFrameMessageAPI.js

iFrameMessageAPI.js

833 ms

trackNewspoolView.js

trackNewspoolView.js

833 ms

cookie.defer.js

cookie.defer.js

834 ms

mobileAppdetector.defer.js

mobileAppdetector.defer.js

881 ms

flipbook.init.defer.js

flipbook.init.defer.js

881 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

882 ms

style.css

style.css

390 ms

bs_multiselect.l3g0.js

bs_multiselect.l3g0.js

817 ms

filter.js

filter.js

742 ms

main.js

main.js

661 ms

dummy.gif

dummy.gif

262 ms

getDocument.ashx

getDocument.ashx

263 ms

getDocument.ashx

getDocument.ashx

321 ms

GetImage.ashx

GetImage.ashx

1376 ms

GetImage.ashx

GetImage.ashx

719 ms

GetImage.ashx

GetImage.ashx

991 ms

GetImage.ashx

GetImage.ashx

416 ms

GetImage.ashx

GetImage.ashx

459 ms

GetImage.ashx

GetImage.ashx

797 ms

GetImage.ashx

GetImage.ashx

1181 ms

GetImage.ashx

GetImage.ashx

748 ms

GetImage.ashx

GetImage.ashx

846 ms

GetImage.ashx

GetImage.ashx

956 ms

GetImage.ashx

GetImage.ashx

882 ms

getDocument.ashx

getDocument.ashx

966 ms

getImage.ashx

getImage.ashx

986 ms

getImage.ashx

getImage.ashx

1050 ms

getImage.ashx

getImage.ashx

1056 ms

getImage.ashx

getImage.ashx

1083 ms

GetImage.ashx

GetImage.ashx

994 ms

GetImage.ashx

GetImage.ashx

1145 ms

GetImage.ashx

GetImage.ashx

1065 ms

ajax-loader.gif

ajax-loader.gif

1090 ms

getDocument.ashx

getDocument.ashx

1085 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

1153 ms

fa-regular-400.ttf

fa-regular-400.ttf

1179 ms

fa-brands-400.ttf

fa-brands-400.ttf

1186 ms

fa-solid-900.ttf

fa-solid-900.ttf

1625 ms

fa-light-300.ttf

fa-light-300.ttf

1311 ms

fa-thin-100.ttf

fa-thin-100.ttf

1238 ms

open-sans-regular.woff

open-sans-regular.woff

176 ms

open-sans-500.woff

open-sans-500.woff

184 ms

open-sans-300.woff

open-sans-300.woff

184 ms

open-sans-600.woff

open-sans-600.woff

568 ms

open-sans-700.woff

open-sans-700.woff

264 ms

open-sans-800.woff

open-sans-800.woff

552 ms

Accessibility Review

hallein.at accessibility score

96

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

hallein.at best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hallein.at SEO score

88

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hallein.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Hallein.at main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

hallein.at

Open Graph description is not detected on the main page of Hallein. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: