1.2 sec in total
297 ms
767 ms
102 ms
Click here to check amazing Grails content for Ireland. Otherwise, check out these important facts you probably never knew about grails.org
A powerful Groovy-based web application framework for the JVM built on top of Spring Boot
Visit grails.orgWe analyzed Grails.org page load time and found that the first response time was 297 ms and then it took 869 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
grails.org performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value2.4 s
92/100
25%
Value1.6 s
100/100
10%
Value270 ms
82/100
30%
Value0.025
100/100
15%
Value6.6 s
58/100
10%
297 ms
16 ms
36 ms
38 ms
447 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Grails.org, 3% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Yourkit.com. The less responsive or slowest element that took the longest time to load (447 ms) relates to the external source Yourkit.com.
Page size can be reduced by 261.7 kB (39%)
668.2 kB
406.4 kB
In fact, the total size of Grails.org main page is 668.2 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. 40% of websites need less resources to load. Images take 347.7 kB which makes up the majority of the site volume.
Potential reduce by 14.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. This page needs HTML code to be minified as it can gain 4.4 kB, which is 24% 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 14.2 kB or 79% of the original size.
Potential reduce by 24.2 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. Grails images are well optimized though.
Potential reduce by 98.1 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 98.1 kB or 66% of the original size.
Potential reduce by 125.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. Grails.org needs all CSS files to be minified and compressed as it can save up to 125.2 kB or 82% of the original size.
Number of requests can be reduced by 8 (15%)
54
46
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grails. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
grails.org
297 ms
bootstrap.css
16 ms
font-awesome.min.css
36 ms
style.css
38 ms
yklogo.png
447 ms
jquery-1.10.2.min.js
48 ms
bootstrap.js
69 ms
modernizr.min.js
77 ms
classie.js
67 ms
sidebarEffects.js
37 ms
plugins.js
36 ms
grails-cupsonly-logo-white.svg
39 ms
artifactory.png
44 ms
pws-thumb.png
64 ms
css
99 ms
greach2016.png
35 ms
gr8confeu2016.png
31 ms
gr8confus2016.png
36 ms
netflix.png
29 ms
amadeus.png
28 ms
bestbuy.png
30 ms
carfax.png
42 ms
carriots.png
47 ms
cisco.png
41 ms
credit-suisse.png
47 ms
airbusgroup.png
54 ms
energy-transfer.png
60 ms
epo.png
57 ms
fanniemae.png
58 ms
google.png
65 ms
hypoport.png
62 ms
ibm.png
78 ms
jpmorganchase.png
71 ms
linkedin.png
76 ms
mastercard.png
72 ms
mtv.png
87 ms
commerzbank.png
89 ms
national-cancer-institute.png
95 ms
nielsen.png
87 ms
nestle.png
94 ms
oracle.png
103 ms
paterson-cancer-institute.png
97 ms
roche.png
100 ms
sas.png
91 ms
sky.png
97 ms
sony.png
153 ms
smartthings.png
102 ms
target.png
102 ms
thales.png
154 ms
ubs.png
153 ms
fontawesome-webfont.woff
156 ms
vodafone.png
132 ms
voyages-sncf.png
132 ms
walmart.png
131 ms
wells-fargo.png
132 ms
icons-colset-2-its.png
127 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
35 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
41 ms
grails.org 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.
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
grails.org 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
grails.org 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grails.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Grails.org 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.
grails.org
Open Graph description is not detected on the main page of Grails. 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: