7.8 sec in total
551 ms
6 sec
1.2 sec
Welcome to fgz.co.at homepage info - get ready to check Fgz best content right away, or after learning these important things about fgz.co.at
Visit fgz.co.atWe analyzed Fgz.co.at page load time and found that the first response time was 551 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fgz.co.at performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value7.5 s
4/100
25%
Value8.7 s
16/100
10%
Value510 ms
57/100
30%
Value0.232
54/100
15%
Value10.8 s
22/100
10%
551 ms
894 ms
205 ms
9 ms
510 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fgz.co.at, 45% (45 requests) were made to Frauengesundheitszentrum.eu and 14% (14 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Frauengesundheitszentrum.eu.
Page size can be reduced by 929.4 kB (35%)
2.6 MB
1.7 MB
In fact, the total size of Fgz.co.at main page is 2.6 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 24.3 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 24.3 kB or 80% of the original size.
Potential reduce by 168.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. Obviously, Fgz needs image optimization as it can save up to 168.5 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 551.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 551.0 kB or 69% of the original size.
Potential reduce by 185.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. Fgz.co.at needs all CSS files to be minified and compressed as it can save up to 185.6 kB or 84% of the original size.
Number of requests can be reduced by 29 (31%)
93
64
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fgz. 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 5 to 1 for CSS and as a result speed up the page load time.
fgz.co.at
551 ms
www.frauengesundheitszentrum.eu
894 ms
front.css
205 ms
bootstrap.min.css
9 ms
fgz.css
510 ms
jquery.min.js
26 ms
zilla-likes.js
206 ms
jquery-ui.min.js
45 ms
bootstrap.min.js
12 ms
modernizr.custom.min.js
206 ms
imagelightbox.min.js
206 ms
jquery.ba-throttle-debounce.min.js
218 ms
jquery-responsive-headlines.min.js
406 ms
jquery.hoverIntent.minified.js
412 ms
jquery.cookie.js
413 ms
bst.js
413 ms
maps
104 ms
logo_RGB.jpg
307 ms
logo-website.jpg
308 ms
slider7.jpg
410 ms
slider6.jpg
512 ms
slider5.jpg
821 ms
slider4.jpg
306 ms
slider8.jpg
611 ms
Slide_Team_neu.jpg
1493 ms
slider2.jpg
712 ms
slider1.jpg
978 ms
was-gibts-neues_.jpg
1025 ms
button1.jpg
816 ms
hover2.jpg
976 ms
button2.jpg
1115 ms
hover3.jpg
1112 ms
button3.jpg
1217 ms
hover4.jpg
1215 ms
button4.jpg
1246 ms
hover5.jpg
1316 ms
button5.jpg
1314 ms
hover6.jpg
1416 ms
button6.jpg
1415 ms
online-beratung.jpg
1850 ms
button7.jpg
1515 ms
Button-8-neu.jpg
3761 ms
button8.jpg
1615 ms
hover10.jpg
1613 ms
button10.jpg
1680 ms
freundinnen.jpg
1816 ms
button9.jpg
1817 ms
292D1B_7_0.woff
1886 ms
fontawesome-webfont.woff
2053 ms
glyphicons-halflings-regular.woff
8 ms
292D1B_8_0.woff
2125 ms
embed
590 ms
analytics.js
49 ms
collect
13 ms
js
88 ms
init_embed.js
50 ms
common.js
60 ms
map.js
85 ms
google4.png
41 ms
overlay.js
38 ms
util.js
102 ms
onion.js
102 ms
search_impl.js
103 ms
StaticMapService.GetMapImage
364 ms
stats.js
51 ms
openhand_8_8.cur
75 ms
ViewportInfoService.GetViewportInfo
151 ms
ViewportInfoService.GetViewportInfo
147 ms
kh
143 ms
transparent.png
37 ms
kh
169 ms
controls.js
21 ms
kh
198 ms
kh
229 ms
kh
236 ms
kh
153 ms
kh
160 ms
kh
152 ms
kh
154 ms
css
138 ms
entity11.png
77 ms
mapcnt6.png
77 ms
tmapctrl.png
72 ms
ViewportInfoService.GetViewportInfo
48 ms
vt
113 ms
vt
49 ms
vt
113 ms
vt
91 ms
vt
93 ms
vt
109 ms
vt
94 ms
vt
157 ms
vt
129 ms
vt
139 ms
vt
137 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
23 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
30 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
30 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
36 ms
AuthenticationService.Authenticate
28 ms
fgz-print.css
205 ms
fgz.co.at accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
fgz.co.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
fgz.co.at 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fgz.co.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fgz.co.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.
fgz.co.at
Open Graph description is not detected on the main page of Fgz. 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: