6 sec in total
1.4 sec
4.4 sec
189 ms
Welcome to grn.es homepage info - get ready to check GRN best content for Spain right away, or after learning these important things about grn.es
Visit grn.esWe analyzed Grn.es page load time and found that the first response time was 1.4 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
grn.es performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value5.3 s
21/100
25%
Value6.6 s
37/100
10%
Value640 ms
46/100
30%
Value0.031
100/100
15%
Value9.2 s
32/100
10%
1356 ms
500 ms
631 ms
835 ms
834 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Grn.es, 69% (60 requests) were made to Grn.cat and 18% (16 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Grn.cat.
Page size can be reduced by 492.2 kB (36%)
1.4 MB
859.0 kB
In fact, the total size of Grn.es main page is 1.4 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 809.4 kB which makes up the majority of the site volume.
Potential reduce by 39.1 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 39.1 kB or 79% of the original size.
Potential reduce by 67.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. GRN images are well optimized though.
Potential reduce by 196.2 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 196.2 kB or 73% of the original size.
Potential reduce by 189.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. Grn.es needs all CSS files to be minified and compressed as it can save up to 189.2 kB or 84% of the original size.
Number of requests can be reduced by 50 (58%)
86
36
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
grn.es
1356 ms
language-selector.css
500 ms
navigation.css
631 ms
cms-navigation-base.css
835 ms
cms-navigation.css
834 ms
css-front.css
890 ms
bootstrap_tab.min.css
868 ms
bootstrap_dropdown.min.css
1104 ms
res_tab_icon.css
869 ms
cli-style.css
1074 ms
flexslider.css
1095 ms
font-awesome.min.css
1125 ms
shortcodes.css
1140 ms
style.css
1264 ms
responsive.css
1184 ms
style.css
1205 ms
style.css
1248 ms
shortcodes.css
1260 ms
general_foundicons.css
1271 ms
social_foundicons.css
1307 ms
otw_shortcode.css
1430 ms
jquery.js
1740 ms
jquery-migrate.js
1379 ms
cookielawinfo.js
1398 ms
responsive-modernizr.js
1399 ms
otw_shortcode_core.js
1426 ms
otw_shortcode.js
1496 ms
sitepress.js
1573 ms
jquery.flexslider-min.js
1444 ms
jquery.fitvids.js
1437 ms
shortcodes.js
1459 ms
responsive-scripts.js
1513 ms
jquery.placeholder.js
1571 ms
bootstrap-dropdown.js
1586 ms
bootstrap-tab.js
1580 ms
bootstrap-tabdrop.js
1584 ms
wp-embed.js
1320 ms
twemoji.js
1246 ms
wp-emoji.js
1043 ms
logo_sg2.png
329 ms
logo_web.png
247 ms
nav-arrow-down.png
246 ms
ca.png
246 ms
en.png
247 ms
es.png
248 ms
baners_web_grn_01.png
697 ms
baners_web_grn_02.png
671 ms
baners_web_grn_03.png
861 ms
baners_web_grn_04.png
813 ms
MTIwMTIwbm9ncm5fMjVfbWFpbA==.jpg
478 ms
MTIwMTIwbm9Qb2xpZ29uUml1ZGVsbG90cw==.jpg
474 ms
MjAwMTAwbm9sb2dvX2Nsb3VkX25ld3M=.png
613 ms
MjAwMTAwbm9BbGl4XzJEMw==.jpg
624 ms
MjAwMTAwbm9Bc3Rlcmlza1BCWA==.png
736 ms
MjAwMTAwbm9jdXJyZW50MTAwYQ==.png
847 ms
MjAwMTAwbm9SYXNwYmVycnk=.png
791 ms
MjAwMTAwbm9BcmR1aW5vVW5vMQ==.jpg
892 ms
twitter-icon.png
915 ms
logo_com-tech.jpg
625 ms
widgets.js
79 ms
overlay.png
906 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
138 ms
syndication
97 ms
624593207897145344
317 ms
1f44d.png
151 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
38 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
80 ms
logo_quadrat_normal.png
123 ms
bcxkNGSJ_normal.png
147 ms
joGargot_normal.jpg
175 ms
28d7c7fe5d5c39b7dbd4996f24037120_normal.png
198 ms
pzJJIafu_normal.jpeg
204 ms
fwqTTuBU_normal.jpg
223 ms
CUfCQhsXAAAO85G.jpg:small
225 ms
CIf4e7mXAAAU3d7.jpg:small
309 ms
CIdKUobWgAAPFhE.jpg:small
258 ms
CIckjobWgAIp1TL.jpg:small
255 ms
CIcZfHUW8AAtvbm.jpg:small
236 ms
CIcU55oWoAAj6vK.jpg:small
300 ms
CIcUYzYXAAAyag0.jpg:small
276 ms
CIcQ6lEWoAAZlYF.jpg:small
289 ms
CIcLQT8WcAA85xE.jpg:small
309 ms
CHoghdoXAAE0MwO.jpg:small
305 ms
jot
32 ms
shortcodes-tablet.css
127 ms
shortcodes-mobile.css
128 ms
bg_direction_nav.png
159 ms
grn.es 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
Links do not have a discernible name
grn.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
grn.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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
CA
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grn.es can be misinterpreted by Google and other search engines. Our service has detected that Catalan is used on the page, and it matches the claimed language. Our system also found out that Grn.es 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.
grn.es
Open Graph description is not detected on the main page of GRN. 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: