5 sec in total
578 ms
4.3 sec
145 ms
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.atWe analyzed Linzag.at page load time and found that the first response time was 578 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
linzag.at performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value9.7 s
0/100
25%
Value11.5 s
5/100
10%
Value400 ms
68/100
30%
Value0.092
91/100
15%
Value14.8 s
8/100
10%
578 ms
196 ms
1495 ms
999 ms
176 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 96% of them (52 requests) were addressed to the original Linzag.at, 2% (1 request) were made to Code.etracker.com and 2% (1 request) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Linzag.at.
Page size can be reduced by 333.7 kB (64%)
520.0 kB
186.3 kB
In fact, the total size of Linzag.at main page is 520.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 260.0 kB which makes up the majority of the site volume.
Potential reduce by 29.6 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 4.8 kB, which is 13% 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 29.6 kB or 83% of the original size.
Potential reduce by 14.0 kB
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. Obviously, LINZ AG needs image optimization as it can save up to 14.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 208.4 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 208.4 kB or 80% of the original size.
Potential reduce by 81.6 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 needs all CSS files to be minified and compressed as it can save up to 81.6 kB or 84% of the original size.
Number of requests can be reduced by 21 (40%)
52
31
The browser has sent 52 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 and as a result speed up the page load time.
linzag.at
578 ms
centerWindow
196 ms
all.js
1495 ms
all.css
999 ms
logo.gif
176 ms
FruehjahrGB2016_StartseitenSujet.jpg
960 ms
timetable-h3-en.gif
305 ms
plus.gif
295 ms
bullet.gif
296 ms
feedback-h3.gif
296 ms
Linz_Nacht_TeaserImage.jpg
650 ms
LenzKinder_TeaserImage.jpg
406 ms
RKL_Asten_TeaserImage.jpg
404 ms
Hafen_Nacht_TeaserImage.jpg
407 ms
PBB_TeaserImage.jpg
408 ms
search-string.gif
656 ms
search-submit.gif
657 ms
tools-separator.gif
655 ms
tab-individual-out_en.gif
656 ms
tab-individual-hover_en.gif
759 ms
tab-individual-active_en.gif
764 ms
tab-customer-out_en.gif
765 ms
tab-customer-hover_en.gif
766 ms
tab-customer-active_en.gif
765 ms
tab-about-out_en.gif
965 ms
tab-about-hover_en.gif
966 ms
tab-about-active_en.gif
967 ms
at-flag.gif
968 ms
nav-drop-bullet.gif
966 ms
nav-drop-bot.png
1205 ms
quicklinks_button.png
1210 ms
quicklinks_hover.png
1209 ms
quicklinks_top.png
1214 ms
quicklinks_bottom.png
1212 ms
header.gif
1214 ms
lnk-top.gif
1365 ms
lnk-print.gif
1364 ms
Icon_Google+.gif
1360 ms
Icon_YouTube.gif
1361 ms
Icon_Twitter.gif
1354 ms
t.js
325 ms
Icon_FB.gif
1195 ms
footer-separator.gif
1207 ms
fieldset.gif
1208 ms
button.png
1202 ms
btn-hindered.gif
1202 ms
cnt_js.php
211 ms
bg_navbutton.png
1102 ms
lnk-calendar.gif
1101 ms
ui-bg_flat_75_ffffff_40x100.png
1251 ms
www.linzag.at.print.css
228 ms
btn-decrease.gif
111 ms
btn-reset.gif
110 ms
btn-increase.gif
111 ms
linzag.at accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
linzag.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
linzag.at SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
EN
ISO-8859-1
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 does not match the claimed English language. Our system also found out that Linzag.at main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
linzag.at
Open Graph description is not detected on the main page of LINZ AG. 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: