6.6 sec in total
363 ms
5.3 sec
945 ms
Click here to check amazing Gracie content. Otherwise, check out these important facts you probably never knew about gracie.eu
Visit gracie.euWe analyzed Gracie.eu page load time and found that the first response time was 363 ms and then it took 6.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.
gracie.eu performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value16.2 s
0/100
25%
Value8.7 s
16/100
10%
Value2,120 ms
7/100
30%
Value0
100/100
15%
Value21.3 s
1/100
10%
363 ms
623 ms
839 ms
1050 ms
22 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Gracie.eu, 65% (32 requests) were made to Linet.com and 8% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Linet.com.
Page size can be reduced by 270.6 kB (6%)
4.3 MB
4.0 MB
In fact, the total size of Gracie.eu main page is 4.3 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. 50% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 178.8 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 46.4 kB, which is 22% 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 178.8 kB or 86% of the original size.
Potential reduce by 8.8 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. Gracie images are well optimized though.
Potential reduce by 61.6 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 61.6 kB or 14% of the original size.
Potential reduce by 21.4 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. Gracie.eu needs all CSS files to be minified and compressed as it can save up to 21.4 kB or 35% of the original size.
Number of requests can be reduced by 17 (44%)
39
22
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gracie. 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 4 to 1 for CSS and as a result speed up the page load time.
gracie.eu
363 ms
cs
623 ms
cs
839 ms
1050 ms
style.css
22 ms
api.js
123 ms
polyfill.min.js
730 ms
jquery-3.6.0.min.js
109 ms
app.js
104 ms
jquery.validate.min.js
110 ms
messages_cs.js
505 ms
jquery.validate.unobtrusive.min.js
115 ms
jquery.unobtrusive-ajax.min.js
113 ms
form.validate.js
113 ms
form.tracking.js
121 ms
form.conditions.js
118 ms
formsextensions.validate.js
122 ms
gtm.js
176 ms
icons-svg.svg
49 ms
Essenza_hero_banner_1920x1440.png
52 ms
Lateral-tilt--decubits-check-render.jpg
59 ms
2_Patient-Transport.jpg
61 ms
safesense3_hero-banner.jpg
60 ms
brand1_new.jpg
64 ms
MulticareX_solutions-component_solution2_1580x1130.jpg
597 ms
AboutMainPortfolio_1580x1130_CZ.png
725 ms
aftersales_image32component.jpg
72 ms
nejlepsi-nemocnice-01.jpg
1184 ms
putovni-soska.png
1409 ms
brussels-picture-2.png
1902 ms
pegasus.JPG
1016 ms
konto-Bariery.jpg
605 ms
about_story_designed_1580x1130.jpg
614 ms
GT-America-Standard-Regular.woff
901 ms
GT-America-Standard-Medium.woff
1243 ms
recaptcha__cs.js
33 ms
js
78 ms
GT-America-Extended-Regular.woff
1264 ms
GT-America-Extended-Medium.woff
1383 ms
fallback
30 ms
fallback
47 ms
fallback
46 ms
landing
90 ms
fallback__ltr.css
4 ms
css
30 ms
logo_48.png
5 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
18 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
print.css
405 ms
gracie.eu 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
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.
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
gracie.eu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
gracie.eu 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
CS
CS
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gracie.eu can be misinterpreted by Google and other search engines. Our service has detected that Czech is used on the page, and it matches the claimed language. Our system also found out that Gracie.eu 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.
gracie.eu
Open Graph description is not detected on the main page of Gracie. 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: