1.4 sec in total
34 ms
1.2 sec
155 ms
Visit repo.grails.org now to see the best up-to-date Repo Grails content for Ireland and also check out these interesting facts you probably never knew about repo.grails.org
Visit repo.grails.orgWe analyzed Repo.grails.org page load time and found that the first response time was 34 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
repo.grails.org performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value59.2 s
0/100
25%
Value21.6 s
0/100
10%
Value11,440 ms
0/100
30%
Value0.048
99/100
15%
Value60.6 s
0/100
10%
34 ms
4 ms
47 ms
58 ms
223 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that all of those requests were addressed to Repo.grails.org and no external sources were called. The less responsive or slowest element that took the longest time to load (223 ms) belongs to the original domain Repo.grails.org.
Page size can be reduced by 3.7 MB (90%)
4.2 MB
422.7 kB
In fact, the total size of Repo.grails.org main page is 4.2 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. 45% of websites need less resources to load. CSS take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 10.5 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.0 kB, which is 31% 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.5 kB or 81% of the original size.
Potential reduce by 3.7 MB
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. Repo.grails.org needs all CSS files to be minified and compressed as it can save up to 3.7 MB or 90% of the original size.
Number of requests can be reduced by 11 (39%)
28
17
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Repo 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 12 to 1 for JavaScripts and as a result speed up the page load time.
repo.grails.org
34 ms
4 ms
47 ms
vendorStyles.40139.css
58 ms
application.40139.css
223 ms
vendorScripts.40139.js
188 ms
templates.40139.js
117 ms
artifactory_core.40139.js
36 ms
artifactory_services.40139.js
50 ms
artifactory_dao.40139.js
106 ms
artifactory_ui.40139.js
105 ms
artifactory_ui_components.40139.js
109 ms
artifactory_directives.40139.js
133 ms
artifactory_filters.40139.js
105 ms
artifactory_views.40139.js
113 ms
artifactory_states.40139.js
192 ms
artifactory_main.40139.js
132 ms
OpenSans-Regular-webfont.40139.woff
20 ms
OpenSans-Light-webfont.40139.woff
19 ms
OpenSans-Semibold-webfont.40139.woff
20 ms
OpenSans-Bold-webfont.40139.woff
20 ms
OpenSans-ExtraBold-webfont.40139.woff
19 ms
current
110 ms
current
111 ms
footer
90 ms
current
90 ms
current
90 ms
footer
82 ms
current
156 ms
current
178 ms
current
169 ms
current
182 ms
current
176 ms
current
170 ms
current
183 ms
current
189 ms
repo.grails.org 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
[aria-*] attributes do not match their roles
[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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
repo.grails.org 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
repo.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 Repo.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 Repo.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.
repo.grails.org
Open Graph description is not detected on the main page of Repo 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: