Tools & Wizards About Us
grails.org screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

grails.org

Grails® Framework

Page Load Speed

857 ms in total

First Response

46 ms

Resources Loaded

486 ms

Page Rendered

325 ms

grails.org screenshot

About Website

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.org

Key Findings

We analyzed Grails.org page load time and found that the first response time was 46 ms and then it took 811 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.

Performance Metrics

grails.org performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.6 s

88/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.225

55/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

grails.org

46 ms

grails.org

43 ms

3cOPSgo5Omz84ycX7CvigfX4cpw.js

10 ms

screen.css

58 ms

plugin.css

62 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 90% of them (38 requests) were addressed to the original Grails.org, 7% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (305 ms) belongs to the original domain Grails.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.1 kB (27%)

Content Size

571.7 kB

After Optimization

418.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Grails.org main page is 571.7 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. 45% of websites need less resources to load. Images take 535.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 10.8 kB

  • Original 14.6 kB
  • After minification 12.0 kB
  • After compression 3.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 2.6 kB, which is 18% 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 10.8 kB or 74% of the original size.

Image Optimization

-27%

Potential reduce by 142.2 kB

  • Original 535.4 kB
  • After minification 393.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. Obviously, Grails needs image optimization as it can save up to 142.2 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 67 B

  • Original 21.6 kB
  • After minification 21.6 kB
  • After compression 21.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 6 (17%)

Requests Now

36

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

grails.org

grails.org

46 ms

grails.org

grails.org

43 ms

3cOPSgo5Omz84ycX7CvigfX4cpw.js

3cOPSgo5Omz84ycX7CvigfX4cpw.js

10 ms

screen.css

screen.css

58 ms

plugin.css

plugin.css

62 ms

paginate.css

paginate.css

61 ms

navigation.js

navigation.js

56 ms

paginate.js

paginate.js

78 ms

plugins.js

plugins.js

55 ms

email-decode.min.js

email-decode.min.js

55 ms

analytics.js

analytics.js

20 ms

collect

collect

23 ms

js

js

58 ms

collect

collect

11 ms

grails_logo.svg

grails_logo.svg

37 ms

banner.png

banner.png

141 ms

flatlearningcurve.png

flatlearningcurve.png

33 ms

springboot.svg

springboot.svg

40 ms

java.png

java.png

43 ms

groovy.png

groovy.png

44 ms

gorm.png

gorm.png

141 ms

restapis.svg

restapis.svg

141 ms

plugins.svg

plugins.svg

158 ms

view.svg

view.svg

154 ms

asynchronous.svg

asynchronous.svg

305 ms

opensource.svg

opensource.svg

155 ms

dsl.png

dsl.png

159 ms

idesupport.png

idesupport.png

159 ms

gr8confeu.png

gr8confeu.png

164 ms

greach.png

greach.png

159 ms

testimoniallogos.png

testimoniallogos.png

167 ms

foundation-logo-horizontal-orange.svg

foundation-logo-horizontal-orange.svg

164 ms

email.svg

email.svg

160 ms

slack.svg

slack.svg

223 ms

youtube.svg

youtube.svg

224 ms

linkedin.svg

linkedin.svg

222 ms

github.svg

github.svg

219 ms

x-twitter.svg

x-twitter.svg

225 ms

roboto-regular.woff

roboto-regular.woff

30 ms

archia-thin.woff

archia-thin.woff

27 ms

roboto-light.woff

roboto-light.woff

42 ms

archia-light.woff

archia-light.woff

43 ms

Accessibility Review

grails.org accessibility score

89

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best Practices

grails.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

grails.org SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

grails.org

Open Graph data is detected on the main page of Grails. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: