2.8 sec in total
442 ms
1.9 sec
468 ms
Visit webnode.cat now to see the best up-to-date Webnode content for Spain and also check out these interesting facts you probably never knew about webnode.cat
Crea tu página web con nuestro editor. Webnode te ofrece hosting y dominio a precios asequibles. Además de eso, cuentas con nuestro soporte local ?.
Visit webnode.catWe analyzed Webnode.cat page load time and found that the first response time was 442 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
webnode.cat performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.4 s
2/100
25%
Value7.2 s
30/100
10%
Value370 ms
71/100
30%
Value0.26
47/100
15%
Value8.4 s
38/100
10%
442 ms
80 ms
77 ms
152 ms
73 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webnode.cat, 72% (64 requests) were made to D1rv23qj5kas56.cloudfront.net and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (450 ms) relates to the external source D1rv23qj5kas56.cloudfront.net.
Page size can be reduced by 398.4 kB (45%)
885.7 kB
487.3 kB
In fact, the total size of Webnode.cat main page is 885.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. 70% of websites need less resources to load. Javascripts take 430.0 kB which makes up the majority of the site volume.
Potential reduce by 23.6 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 23.6 kB or 76% of the original size.
Potential reduce by 28.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. Webnode images are well optimized though.
Potential reduce by 271.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 271.2 kB or 63% of the original size.
Potential reduce by 74.9 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. Webnode.cat needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 80% of the original size.
Number of requests can be reduced by 48 (62%)
77
29
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webnode. 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.
www.webnode.cat
442 ms
css
80 ms
webnode.package.1-1-109.css
77 ms
webnode.package.extended.1-1-109.js
152 ms
ca.type1.1.15.js
73 ms
gtm.js
269 ms
analytics.js
267 ms
dc.js
390 ms
bgrPageFull.png
209 ms
bgrHeaderHome2.jpg
221 ms
elementsInHeader4.png
216 ms
webnodeLogo3.png
233 ms
bgrHeaderMenu.png
233 ms
elementsInHeader2.png
236 ms
homepage2.jpg
323 ms
bgrHomepageBlocks.png
307 ms
bgrThreeBlocksIcon.png
301 ms
techcrunch.png
275 ms
loading.gif
273 ms
blog-mobil-2.png
289 ms
bgrFormElementsHeader2.png
298 ms
bgrFormHintHeaderForms.png
299 ms
bgrSignIn3.png
314 ms
bgrFormElements2.png
311 ms
top_bg.jpg
312 ms
delimiter.png
312 ms
de.png
310 ms
at.png
377 ms
en.png
378 ms
en-in.png
376 ms
us.png
383 ms
es.png
383 ms
es-ar.png
382 ms
es-cl.png
410 ms
es-co.png
409 ms
es-mx.png
405 ms
es-uy.png
404 ms
es-ve.png
410 ms
fr.png
410 ms
fr-be.png
450 ms
it.png
449 ms
hu.png
450 ms
nl.png
449 ms
IgZJs4-7SA1XX_edsoXWog.ttf
181 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
253 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
296 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
300 ms
Uxzkqj-MIMWle-XP2pDNAA.ttf
301 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
299 ms
7MygqTe2zs9YkP0adA9QQQ.ttf
300 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
294 ms
H1vB34nOKWXqzKotq25pcg.ttf
306 ms
nl-be.png
294 ms
no.png
257 ms
pl.png
263 ms
pt.png
263 ms
br.png
247 ms
ro.png
243 ms
conversion_async.js
172 ms
fbds.js
212 ms
collect
51 ms
collect
116 ms
collect
126 ms
sk.png
197 ms
fi.png
196 ms
sv.png
205 ms
tr.png
202 ms
vi.png
195 ms
cz.png
193 ms
el.png
194 ms
ru.png
192 ms
uk.png
187 ms
ja.png
187 ms
tw.png
185 ms
ko.png
184 ms
icon_facebook.png
185 ms
icon_twitter.png
182 ms
__utm.gif
40 ms
icon_googleplus.png
122 ms
bullet_lang_closed.png
122 ms
bottom_bg.jpg
115 ms
webnode_logo_footer2.png
121 ms
rotorblog.png
121 ms
ga-audiences
112 ms
76 ms
102 ms
16 ms
signupLoading.gif
7 ms
21 ms
webnode.cat 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
webnode.cat 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
webnode.cat 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
Image elements do not have [alt] attributes
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
ES
CA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webnode.cat can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed Catalan language. Our system also found out that Webnode.cat 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.
webnode.cat
Open Graph description is not detected on the main page of Webnode. 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: