Tools & Wizards About Us
webooks.fr screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

webooks.fr

Blog d'infos utiles - WEBooks

Page Load Speed

4.1 sec in total

First Response

448 ms

Resources Loaded

3.4 sec

Page Rendered

247 ms

webooks.fr screenshot

About Website

Welcome to webooks.fr homepage info - get ready to check WEBooks best content for France right away, or after learning these important things about webooks.fr

Ebooks gratuits. Téléchargement légal et gratuit de livres électroniques, créer vos propres ebooks au format PDF, télechargement gratuit de logciels de gestion, lecture et création d'ebooks, diffusion...

Visit webooks.fr

Key Findings

We analyzed Webooks.fr page load time and found that the first response time was 448 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

webooks.fr performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

96/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,880 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

webooks.fr

448 ms

lightbox.css

130 ms

lightbox.js

269 ms

feuille.css

169 ms

prototype.js

255 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 42% of them (29 requests) were addressed to the original Webooks.fr, 9% (6 requests) were made to Pagead2.googlesyndication.com and 9% (6 requests) were made to Wms.assoc-amazon.fr. The less responsive or slowest element that took the longest time to load (809 ms) relates to the external source Sv2.biz.

Page Optimization Overview & Recommendations

Page size can be reduced by 360.0 kB (54%)

Content Size

664.3 kB

After Optimization

304.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Webooks.fr main page is 664.3 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. 40% of websites need less resources to load. Javascripts take 323.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 31.5 kB

  • Original 40.8 kB
  • After minification 40.0 kB
  • After compression 9.3 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 31.5 kB or 77% of the original size.

Image Optimization

-26%

Potential reduce by 71.7 kB

  • Original 280.4 kB
  • After minification 208.7 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. Obviously, WEBooks needs image optimization as it can save up to 71.7 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 240.5 kB

  • Original 323.4 kB
  • After minification 240.7 kB
  • After compression 82.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 240.5 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 16.2 kB

  • Original 19.6 kB
  • After minification 14.0 kB
  • After compression 3.4 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. Webooks.fr needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (44%)

Requests Now

62

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webooks.fr

webooks.fr

448 ms

lightbox.css

lightbox.css

130 ms

lightbox.js

lightbox.js

269 ms

feuille.css

feuille.css

169 ms

prototype.js

prototype.js

255 ms

scriptaculous.js

scriptaculous.js

187 ms

sin.css

sin.css

61 ms

cook.js

cook.js

63 ms

div.js

div.js

77 ms

q

q

273 ms

show_ads.js

show_ads.js

8 ms

effects.js

effects.js

182 ms

cancel.png

cancel.png

19 ms

plg.png

plg.png

474 ms

20100212095833_728x90_04.gif

20100212095833_728x90_04.gif

809 ms

back_page.jpg

back_page.jpg

193 ms

adobe_reader.jpg

adobe_reader.jpg

93 ms

winrar.jpg

winrar.jpg

93 ms

winzip.jpg

winzip.jpg

101 ms

button.png

button.png

480 ms

fr201109na_336x280_fbdown_02g.jpg

fr201109na_336x280_fbdown_02g.jpg

743 ms

A1.bmp

A1.bmp

365 ms

A2.bmp

A2.bmp

387 ms

A4.bmp

A4.bmp

493 ms

A3.bmp

A3.bmp

448 ms

A5.bmp

A5.bmp

483 ms

A6.bmp

A6.bmp

539 ms

header.jpg

header.jpg

618 ms

ads_display.php

ads_display.php

755 ms

spacer.gif

spacer.gif

30 ms

ca-pub-7592305470410646.js

ca-pub-7592305470410646.js

40 ms

zrt_lookup.html

zrt_lookup.html

43 ms

show_ads_impl.js

show_ads_impl.js

64 ms

menu_back.jpg

menu_back.jpg

244 ms

menu_back_hover.jpg

menu_back_hover.jpg

193 ms

menu_left_top.jpg

menu_left_top.jpg

193 ms

menu_left_back.jpg

menu_left_back.jpg

234 ms

menu_left_bot.jpg

menu_left_bot.jpg

120 ms

8006.js

8006.js

464 ms

ads

ads

210 ms

osd.js

osd.js

5 ms

m_js_controller.js

m_js_controller.js

26 ms

abg.js

abg.js

42 ms

favicon

favicon

44 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

46 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

35 ms

s

s

28 ms

x_button_blue2.png

x_button_blue2.png

10 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

10 ms

popup.js

popup.js

84 ms

nifty.js

nifty.js

158 ms

colors.js

colors.js

165 ms

center_head_back.jpg

center_head_back.jpg

263 ms

A1.bmp

A1.bmp

762 ms

actu.gif

actu.gif

97 ms

menu_right_top.jpg

menu_right_top.jpg

193 ms

ads_display.php

ads_display.php

584 ms

menu_right_bot.jpg

menu_right_bot.jpg

177 ms

footer_back.jpg

footer_back.jpg

284 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

11 ms

spacer.gif

spacer.gif

32 ms

activeview

activeview

14 ms

ir

ir

156 ms

167 ms

widgets.css

widgets.css

84 ms

q

q

85 ms

ui

ui

33 ms

amazon-logo-b_tpng.png

amazon-logo-b_tpng.png

86 ms

Accessibility Review

webooks.fr accessibility score

63

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

webooks.fr best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

webooks.fr SEO score

69

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

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

webooks.fr

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