6.1 sec in total
310 ms
5.3 sec
530 ms
Click here to check amazing Greisinger content. Otherwise, check out these important facts you probably never knew about greisinger.com
Als Familienunternehmen mit langer Meistertradition wissen wir, worauf es besonders ankommt: hohe Qualität der Rohstoffe.
Visit greisinger.comWe analyzed Greisinger.com page load time and found that the first response time was 310 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
greisinger.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value9.2 s
1/100
25%
Value6.9 s
33/100
10%
Value390 ms
69/100
30%
Value0.003
100/100
15%
Value8.5 s
38/100
10%
310 ms
1233 ms
202 ms
200 ms
312 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 85% of them (71 requests) were addressed to the original Greisinger.com, 5% (4 requests) were made to Youtube.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Greisinger.com.
Page size can be reduced by 730.6 kB (50%)
1.5 MB
725.9 kB
In fact, the total size of Greisinger.com main page is 1.5 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 524.4 kB which makes up the majority of the site volume.
Potential reduce by 20.4 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 20.4 kB or 73% of the original size.
Potential reduce by 49.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. Greisinger images are well optimized though.
Potential reduce by 342.0 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 342.0 kB or 66% of the original size.
Potential reduce by 319.2 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. Greisinger.com needs all CSS files to be minified and compressed as it can save up to 319.2 kB or 83% of the original size.
Number of requests can be reduced by 48 (62%)
78
30
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greisinger. 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 30 to 1 for CSS and as a result speed up the page load time.
greisinger.com
310 ms
1233 ms
widgetkit-f207537b.css
202 ms
template.css
200 ms
jquery.min.js
312 ms
jquery-noconflict.js
207 ms
jquery-migrate.min.js
207 ms
widgetkit-de26e690.js
208 ms
base.css
397 ms
layout.css
402 ms
menus.css
399 ms
modules.css
403 ms
tools.css
405 ms
system.css
506 ms
extensions.css
593 ms
custom.css
594 ms
animation.css
599 ms
opensanslight.css
597 ms
opensanslight.css
601 ms
style.css
700 ms
responsive.css
786 ms
easy4U.css
793 ms
print.css
790 ms
opensanslight.css
797 ms
warp.js
796 ms
responsive.js
899 ms
accordionmenu.js
985 ms
dropdownmenu.js
985 ms
template.js
993 ms
search.js
994 ms
lightbox.js
669 ms
mediaelement-and-player.js
871 ms
spotlight.js
853 ms
base.css
797 ms
menus.css
803 ms
layout.css
803 ms
modules.css
802 ms
tools.css
986 ms
system.css
883 ms
system.css
891 ms
system-all.css
898 ms
custom.css
812 ms
responsive.css
622 ms
print.css
796 ms
analytics.js
63 ms
noise_bg3.png
209 ms
bg_streifen.png
210 ms
logo.png
225 ms
noise_bg1.png
226 ms
infinite_teaser1_green.jpg
235 ms
hof_muehlviertel_1680.jpg
604 ms
muehlviertler-meisterqualitaet.png
593 ms
DLG_Medaille_2015.jpg
779 ms
BR_Potpourri.jpg
779 ms
Kabo-Nossa_Logo.jpg
594 ms
Anuga.png
602 ms
prodexpo_2014.png
864 ms
fleischscout_logo.jpg
864 ms
Logo_HOFEX.png
865 ms
marca_2015.jpg
891 ms
logo_onlineshop.png
901 ms
logo_landkost_onlineshop.png
1194 ms
qr-code-greisinger-fleischscout.png
989 ms
fleischscout.png
990 ms
module_icons_white.png
998 ms
Muehlviertler-Meister-Qualitaet.png
1084 ms
de.gif
1099 ms
en.gif
1236 ms
searchbox_magnifier.png
1255 ms
LQhvkxn4iGE
173 ms
U3M01hecMS4
153 ms
vd4HCiVW_r0
144 ms
LT8-xZIxkiY
156 ms
OpenSans-Light-webfont.woff
1334 ms
slideshow.js
1233 ms
collect
16 ms
www-embed-player-vflfNyN_r.css
53 ms
www-embed-player.js
84 ms
base.js
125 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
185 ms
ad_status.js
171 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
175 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
175 ms
raster_bg.png
106 ms
greisinger.com 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
[role] values are not valid
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
greisinger.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
greisinger.com SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greisinger.com 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 Greisinger.com 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.
greisinger.com
Open Graph description is not detected on the main page of Greisinger. 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: