11.5 sec in total
493 ms
8.1 sec
2.9 sec
Visit greiner.at now to see the best up-to-date Greiner content for Austria and also check out these interesting facts you probably never knew about greiner.at
Greiner, which is headquartered in Kremsmünster, Austria, is one of the world’s leading suppliers of plastics and foam solutions.
Visit greiner.atWe analyzed Greiner.at page load time and found that the first response time was 493 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
greiner.at performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.8 s
15/100
25%
Value6.9 s
33/100
10%
Value390 ms
69/100
30%
Value0.496
16/100
15%
Value6.0 s
65/100
10%
493 ms
14 ms
19 ms
17 ms
355 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 95% of them (77 requests) were addressed to the original Greiner.at, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Greiner.at.
Page size can be reduced by 488.3 kB (6%)
8.2 MB
7.7 MB
In fact, the total size of Greiner.at main page is 8.2 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. 70% of websites need less resources to load. Images take 7.6 MB which makes up the majority of the site volume.
Potential reduce by 74.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. 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 74.2 kB or 80% of the original size.
Potential reduce by 72.5 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. Greiner images are well optimized though.
Potential reduce by 214.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 214.9 kB or 66% of the original size.
Potential reduce by 126.7 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. Greiner.at needs all CSS files to be minified and compressed as it can save up to 126.7 kB or 82% of the original size.
Number of requests can be reduced by 33 (41%)
80
47
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greiner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
493 ms
news-basic.css
14 ms
stylesheet_6ef9f0734f.css
19 ms
SrLanguageMenu.css
17 ms
bootstrap.min.css
355 ms
base.css
13 ms
jquery-1.11.0.min.js
366 ms
bootstrap.min.js
240 ms
jquery.stellar.min.js
235 ms
facebox.css
251 ms
facebox.js
250 ms
jquery.bxslider.css
469 ms
jquery.bxslider.min.js
479 ms
flexslider.css
993 ms
jquery.flexslider-min.js
1337 ms
smoothDivScroll.css
388 ms
jquery-ui-1.10.3.custom.min.js
1338 ms
jquery.mousewheel.min.js
2336 ms
jquery.kinetic.min.js
477 ms
jquery.smoothdivscroll-1.3-min.js
2340 ms
jquery.PrintArea.js
481 ms
jquery.validate.min.js
486 ms
greiner_holding_logo_860x400.jpg
2293 ms
icon_facebook.png
1962 ms
icon_twitter.png
2963 ms
icon_youtube.png
2958 ms
axel_kuehner.jpg
2969 ms
hannes_moser.jpg
2966 ms
RTEmagicC_organigramm_de.jpg
3186 ms
RTEmagicC_Maximilian_WELLNER_01.jpg
2964 ms
th_codeofconduct_de.jpg
4076 ms
RTEmagicC_gho_kennzahlen_2014_de.png
3808 ms
GB_2014_Vorschaubild_DE.jpg
4080 ms
GB_2014_Vorschaubild_EN.jpg
4076 ms
GB_2014_Vorschaubild_CN.jpg
4076 ms
slide_historie_1868.png
4309 ms
slide_historie_1878_01.png
4378 ms
slide_historie_1899_01.png
4319 ms
slide_historie_1950_01.png
4538 ms
slide_historie_1952_01.png
4316 ms
slide_historie_1956_01.png
4636 ms
slide_historie_1960_01.png
4317 ms
slide_historie_1963_01.png
4765 ms
slide_historie_1973_01.png
4970 ms
slide_historie_1986_01.png
4971 ms
slide_historie_1989_01.png
4975 ms
slide_historie_1999_01.png
5194 ms
analytics.js
14 ms
slide_historie_2001_01.png
4741 ms
collect
15 ms
slide_historie_2010.png
4896 ms
slide_historie_2012.png
5366 ms
slide_historie_2013.png
5550 ms
slide_history_2014.png
5103 ms
stop.jpg
5116 ms
greinervideo_start.jpg
5034 ms
icon_presse.png
4471 ms
icon_karriere.png
4469 ms
icon_standorte.png
3500 ms
Startseite_Einleitung_Banner_2400x1600.jpg
3706 ms
iframe_api
82 ms
Konzern_Organe_2400x1600.jpg
3643 ms
www-widgetapi.js
17 ms
Konzern_Organigramm_2400x1600.jpg
3300 ms
Konzern_Compliance_Slide1_2400x1600.jpg
3380 ms
Konzern_Compliance_Slide2_2400x1600.jpg
3575 ms
Konzern_Compliance_Slide3_2400x1600.jpg
3410 ms
Konzern_Compliance_Slide4_2400x1600.jpg
3538 ms
Konzern_Compliance_Slide5_2400x1600.jpg
2932 ms
Konzern_Compliance_Slide6_2400x1600.jpg
2721 ms
Konzern_Compliance_Slide7_2400x1600.jpg
2215 ms
video_greiner_group_2014.jpg
2067 ms
Startseite_Standorte_2400x1600.jpg
2193 ms
dropdown_arrow.png
2300 ms
pulldown.png
2422 ms
greiner_holding_logo_86x40.jpg
2266 ms
arrow_left.png
2284 ms
arrow_right.png
2171 ms
papierhg_2400x600.jpg
2402 ms
bx_loader.gif
2355 ms
printjob.css
243 ms
greiner.at accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
greiner.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
greiner.at SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greiner.at can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Greiner.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.
greiner.at
Open Graph description is not detected on the main page of Greiner. 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: