Tools & Wizards About Us
doodle.be screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

doodle.be

Doodle.be change de nom et devient « Parfaitement web »

Page Load Speed

2 sec in total

First Response

320 ms

Resources Loaded

1.5 sec

Page Rendered

127 ms

doodle.be screenshot

About Website

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

Le changement de nom s’inscrit dans la volonté d’une communication et relation encore plus proches et directes avec nos clients.

Visit doodle.be

Key Findings

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

Performance Metrics

doodle.be performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

doodle.be

320 ms

styles.css

620 ms

jquery-1.4.4.min.js

782 ms

cufon-yui.js

622 ms

aaux_reg.font.js

861 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 94% of them (32 requests) were addressed to the original Doodle.be, 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (886 ms) belongs to the original domain Doodle.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.8 kB (69%)

Content Size

721.2 kB

After Optimization

222.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Doodle.be main page is 721.2 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. 25% of websites need less resources to load. Javascripts take 615.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 22.4 kB

  • Original 26.5 kB
  • After minification 26.1 kB
  • After compression 4.2 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 22.4 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 2.2 kB

  • Original 64.3 kB
  • After minification 62.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. Doodle images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 462.9 kB

  • Original 615.9 kB
  • After minification 615.0 kB
  • After compression 153.0 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 462.9 kB or 75% of the original size.

CSS Optimization

-79%

Potential reduce by 11.4 kB

  • Original 14.4 kB
  • After minification 11.7 kB
  • After compression 3.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. Doodle.be needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (55%)

Requests Now

33

After Optimization

15

  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doodle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

doodle.be

doodle.be

320 ms

styles.css

styles.css

620 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

782 ms

cufon-yui.js

cufon-yui.js

622 ms

aaux_reg.font.js

aaux_reg.font.js

861 ms

aauxBold_v2.font.js

aauxBold_v2.font.js

877 ms

aauxItalic_v2.font.js

aauxItalic_v2.font.js

780 ms

aaux_ita.font.js

aaux_ita.font.js

886 ms

typeit.js

typeit.js

705 ms

hover_works.js

hover_works.js

797 ms

active_menu.js

active_menu.js

885 ms

jquery.jtweetsanywhere-1.2.1.min.js

jquery.jtweetsanywhere-1.2.1.min.js

885 ms

ga.js

ga.js

10 ms

dashedBackground.png

dashedBackground.png

90 ms

logo_03.png

logo_03.png

89 ms

curlyMenuAbout.png

curlyMenuAbout.png

91 ms

filet960.png

filet960.png

92 ms

homeAlexis.png

homeAlexis.png

92 ms

homeDorian.png

homeDorian.png

94 ms

homeQuentin.png

homeQuentin.png

170 ms

twitterBubble.png

twitterBubble.png

171 ms

facebookBubble.png

facebookBubble.png

172 ms

lineFB_NL.png

lineFB_NL.png

174 ms

newsletterIcon1.png

newsletterIcon1.png

173 ms

lta.jpg

lta.jpg

176 ms

LastProjectOpenSite.png

LastProjectOpenSite.png

254 ms

headBubble.png

headBubble.png

253 ms

curlySocial.png

curlySocial.png

252 ms

filetHorizSocial.png

filetHorizSocial.png

249 ms

lastProjectFrame.png

lastProjectFrame.png

251 ms

lastProjectCurlyRight.png

lastProjectCurlyRight.png

253 ms

lastProjectCurlyLeft.png

lastProjectCurlyLeft.png

330 ms

lastProjectBubble2.png

lastProjectBubble2.png

331 ms

__utm.gif

__utm.gif

12 ms

Accessibility Review

doodle.be 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.

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

Links do not have a discernible name

Best Practices

doodle.be 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

doodle.be 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

    FR

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doodle.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Doodle.be main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

doodle.be

Open Graph description is not detected on the main page of Doodle. 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: