Tools & Wizards About Us
webnode.be screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    56% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

webnode.be

Gratis website maken - Webnode

Page Load Speed

2.4 sec in total

First Response

362 ms

Resources Loaded

1.5 sec

Page Rendered

544 ms

webnode.be screenshot

About Website

Welcome to webnode.be homepage info - get ready to check Webnode best content for Belgium right away, or after learning these important things about webnode.be

Bouw jouw website eenvoudig met de Webnode editor. Domeinnamen en hosting zijn inbegrepen. De snelle en lokale ondersteuning

Visit webnode.be

Key Findings

We analyzed Webnode.be page load time and found that the first response time was 362 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

webnode.be performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

www.webnode.be

362 ms

css

90 ms

webnode.package.1-1-109.css

80 ms

webnode.package.basic.1-1-109.js

83 ms

nl.type1.1.15.js

77 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webnode.be, 73% (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 (385 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.1 kB (42%)

Content Size

775.8 kB

After Optimization

452.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webnode.be main page is 775.8 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 330.5 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 24.3 kB

  • Original 32.3 kB
  • After minification 31.9 kB
  • After compression 8.0 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 24.3 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 28.7 kB

  • Original 330.5 kB
  • After minification 301.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.

JavaScript Optimization

-61%

Potential reduce by 191.7 kB

  • Original 314.6 kB
  • After minification 314.6 kB
  • After compression 122.9 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 191.7 kB or 61% of the original size.

CSS Optimization

-80%

Potential reduce by 78.5 kB

  • Original 98.5 kB
  • After minification 98.1 kB
  • After compression 20.0 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.be needs all CSS files to be minified and compressed as it can save up to 78.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

77

After Optimization

29

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

www.webnode.be

www.webnode.be

362 ms

css

css

90 ms

webnode.package.1-1-109.css

webnode.package.1-1-109.css

80 ms

webnode.package.basic.1-1-109.js

webnode.package.basic.1-1-109.js

83 ms

nl.type1.1.15.js

nl.type1.1.15.js

77 ms

bgrPageFull.png

bgrPageFull.png

163 ms

gtm.js

gtm.js

165 ms

analytics.js

analytics.js

161 ms

dc.js

dc.js

161 ms

bgrHeaderHome2.jpg

bgrHeaderHome2.jpg

97 ms

elementsInHeader4.png

elementsInHeader4.png

103 ms

webnodeLogo3.png

webnodeLogo3.png

103 ms

bgrHeaderMenu.png

bgrHeaderMenu.png

117 ms

elementsInHeader2.png

elementsInHeader2.png

107 ms

homepage2.jpg

homepage2.jpg

119 ms

bgrHomepageBlocks.png

bgrHomepageBlocks.png

117 ms

bgrThreeBlocksIcon.png

bgrThreeBlocksIcon.png

123 ms

techcrunch.png

techcrunch.png

139 ms

loading.gif

loading.gif

130 ms

blog-mobil-2.png

blog-mobil-2.png

145 ms

bgrFormElementsHeader2.png

bgrFormElementsHeader2.png

139 ms

bgrFormHintHeaderForms.png

bgrFormHintHeaderForms.png

137 ms

bgrSignIn3.png

bgrSignIn3.png

138 ms

bgrFormElements2.png

bgrFormElements2.png

145 ms

top_bg.jpg

top_bg.jpg

149 ms

delimiter.png

delimiter.png

148 ms

ca.png

ca.png

149 ms

de.png

de.png

150 ms

at.png

at.png

151 ms

en.png

en.png

154 ms

en-in.png

en-in.png

178 ms

us.png

us.png

155 ms

es.png

es.png

168 ms

es-ar.png

es-ar.png

152 ms

es-cl.png

es-cl.png

178 ms

es-co.png

es-co.png

178 ms

es-mx.png

es-mx.png

179 ms

es-uy.png

es-uy.png

177 ms

es-ve.png

es-ve.png

178 ms

fr.png

fr.png

187 ms

fr-be.png

fr-be.png

203 ms

it.png

it.png

183 ms

hu.png

hu.png

185 ms

nl-be.png

nl-be.png

184 ms

no.png

no.png

186 ms

IgZJs4-7SA1XX_edsoXWog.ttf

IgZJs4-7SA1XX_edsoXWog.ttf

237 ms

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf

289 ms

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf

343 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

333 ms

Uxzkqj-MIMWle-XP2pDNAA.ttf

Uxzkqj-MIMWle-XP2pDNAA.ttf

344 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

385 ms

7MygqTe2zs9YkP0adA9QQQ.ttf

7MygqTe2zs9YkP0adA9QQQ.ttf

342 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

367 ms

H1vB34nOKWXqzKotq25pcg.ttf

H1vB34nOKWXqzKotq25pcg.ttf

369 ms

collect

collect

109 ms

__utm.gif

__utm.gif

73 ms

conversion_async.js

conversion_async.js

63 ms

fbds.js

fbds.js

159 ms

collect

collect

46 ms

collect

collect

114 ms

pl.png

pl.png

109 ms

pt.png

pt.png

108 ms

br.png

br.png

108 ms

ro.png

ro.png

94 ms

sk.png

sk.png

91 ms

fi.png

fi.png

96 ms

sv.png

sv.png

88 ms

tr.png

tr.png

81 ms

vi.png

vi.png

79 ms

cz.png

cz.png

85 ms

el.png

el.png

74 ms

ru.png

ru.png

75 ms

uk.png

uk.png

84 ms

ja.png

ja.png

83 ms

tw.png

tw.png

78 ms

ko.png

ko.png

77 ms

icon_facebook.png

icon_facebook.png

77 ms

icon_twitter.png

icon_twitter.png

95 ms

icon_googleplus.png

icon_googleplus.png

97 ms

bullet_lang_closed.png

bullet_lang_closed.png

92 ms

bottom_bg.jpg

bottom_bg.jpg

78 ms

webnode_logo_footer2.png

webnode_logo_footer2.png

89 ms

rotorblog.png

rotorblog.png

78 ms

ga-audiences

ga-audiences

122 ms

80 ms

110 ms

signupLoading.gif

signupLoading.gif

62 ms

4 ms

Accessibility Review

webnode.be accessibility score

63

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

webnode.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

webnode.be SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webnode.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Webnode.be 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

webnode.be

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: