Tools & Wizards About Us
linzag.at screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

linzag.at

LINZ AG

Page Load Speed

4.3 sec in total

First Response

310 ms

Resources Loaded

2.6 sec

Page Rendered

1.4 sec

linzag.at screenshot

About Website

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

Die LINZ AG kümmert sich als Multi-Utility-Anbieter um die Energieversorgung, den öffentlichen Nahverkehr und kommunale Dienste in Linz, Oberösterreich.

Visit linzag.at

Key Findings

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

Performance Metrics

linzag.at performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,410 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.716

7/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

linzag.at

310 ms

www.linzag.at

559 ms

home

304 ms

jquery-1.11.3.js

256 ms

theme.css.jsf

350 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 67% of them (20 requests) were addressed to the original Linzag.at, 10% (3 requests) were made to Cdn.cookielaw.org and 7% (2 requests) were made to Services.linzag.at. The less responsive or slowest element that took the longest time to load (958 ms) relates to the external source Services.linzag.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.3 kB (8%)

Content Size

3.0 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Linzag.at main page is 3.0 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. 35% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 233.6 kB

  • Original 265.3 kB
  • After minification 238.7 kB
  • After compression 31.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 233.6 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 17.4 kB

  • Original 2.2 MB
  • After minification 2.2 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. LINZ AG images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 366 B

  • Original 542.8 kB
  • After minification 542.8 kB
  • After compression 542.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 6.0 kB

  • Original 61.1 kB
  • After minification 61.1 kB
  • After compression 55.1 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. Linzag.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

linzag.at

linzag.at

310 ms

www.linzag.at

www.linzag.at

559 ms

home

home

304 ms

jquery-1.11.3.js

jquery-1.11.3.js

256 ms

theme.css.jsf

theme.css.jsf

350 ms

jsf.js.jsf;jsessionid=XntiGNQFTRWeiZ5kIdE7AauvW3_YG62xrxDo1JAI.node1

jsf.js.jsf;jsessionid=XntiGNQFTRWeiZ5kIdE7AauvW3_YG62xrxDo1JAI.node1

354 ms

otSDKStub.js

otSDKStub.js

42 ms

application.css

application.css

563 ms

e.js

e.js

537 ms

styles.css

styles.css

514 ms

efa-presearch-webcomponent.js

efa-presearch-webcomponent.js

958 ms

ro9GFX1p19.js

ro9GFX1p19.js

25 ms

plugin.min.js

plugin.min.js

432 ms

common.min.js

common.min.js

249 ms

d02405ca-bad4-4d47-9951-393ef6fabd67.json

d02405ca-bad4-4d47-9951-393ef6fabd67.json

29 ms

location

location

41 ms

otBannerSdk.js

otBannerSdk.js

18 ms

t.js

t.js

434 ms

page_logo.svg

page_logo.svg

129 ms

page_logo.png

page_logo.png

124 ms

laptop-bestattungsauftrag_heroSlider.jpg

laptop-bestattungsauftrag_heroSlider.jpg

343 ms

cyrano_heroSlider.jpg

cyrano_heroSlider.jpg

591 ms

Fussballderby_heroSlider.jpg

Fussballderby_heroSlider.jpg

465 ms

online-rechnung_heroSlider.jpg

online-rechnung_heroSlider.jpg

715 ms

badge-plus24.png

badge-plus24.png

349 ms

Abfall-App-Sujet_heroSlider.jpg

Abfall-App-Sujet_heroSlider.jpg

364 ms

verstorbenensuche_heroSlider.jpg

verstorbenensuche_heroSlider.jpg

516 ms

blank.gif

blank.gif

465 ms

lag-webfont.ttf

lag-webfont.ttf

577 ms

cntcc

cntcc

418 ms

Accessibility Review

linzag.at accessibility score

68

Accessibility Issues

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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

[id] attributes on active, focusable elements are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

linzag.at best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

linzag.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 Linzag.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 Linzag.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

linzag.at

Open Graph data is detected on the main page of LINZ AG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: