Tools & Wizards About Us
diglee.com screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

diglee.com

Diglee | Mon blog d'illustratrice

Page Load Speed

4.4 sec in total

First Response

286 ms

Resources Loaded

2.2 sec

Page Rendered

1.9 sec

diglee.com screenshot

About Website

Welcome to diglee.com homepage info - get ready to check Diglee best content for France right away, or after learning these important things about diglee.com

Mon blog d'illustratrice

Visit diglee.com

Key Findings

We analyzed Diglee.com page load time and found that the first response time was 286 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

diglee.com performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.5 s

95/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.096

91/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

diglee.com

286 ms

style.css

238 ms

effects.css

164 ms

style_2.1.2.css

165 ms

prototype.js

81 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 33% of them (40 requests) were addressed to the original Diglee.com, 8% (10 requests) were made to Ajax.googleapis.com and 7% (9 requests) were made to Fileserver.mode.com. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Diglee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 706.0 kB (39%)

Content Size

1.8 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Diglee.com main page is 1.8 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. 65% of websites need less resources to load. Images take 929.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 138.5 kB

  • Original 184.1 kB
  • After minification 182.0 kB
  • After compression 45.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 138.5 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 82.6 kB

  • Original 929.6 kB
  • After minification 847.0 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. Diglee images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 438.3 kB

  • Original 643.8 kB
  • After minification 605.6 kB
  • After compression 205.5 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 438.3 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 46.5 kB

  • Original 55.2 kB
  • After minification 44.4 kB
  • After compression 8.6 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. Diglee.com needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 73 (64%)

Requests Now

114

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

diglee.com

diglee.com

286 ms

style.css

style.css

238 ms

effects.css

effects.css

164 ms

style_2.1.2.css

style_2.1.2.css

165 ms

prototype.js

prototype.js

81 ms

scriptaculous.js

scriptaculous.js

91 ms

effects.js

effects.js

103 ms

lightbox.js

lightbox.js

174 ms

jquery.js

jquery.js

427 ms

jquery-migrate.min.js

jquery-migrate.min.js

188 ms

superfish.js

superfish.js

243 ms

woo_tabs.js

woo_tabs.js

245 ms

general.js

general.js

262 ms

default.css

default.css

281 ms

custom.css

custom.css

314 ms

viewChannelModule.act

viewChannelModule.act

135 ms

loader_iconbox.js

loader_iconbox.js

28 ms

viewChannelModule.act

viewChannelModule.act

117 ms

script_2.1.2.js

script_2.1.2.js

241 ms

button.facebook.js

button.facebook.js

242 ms

all.js

all.js

21 ms

reset.css

reset.css

116 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

90 ms

builder.js

builder.js

11 ms

effects.js

effects.js

13 ms

dragdrop.js

dragdrop.js

23 ms

controls.js

controls.js

28 ms

slider.js

slider.js

33 ms

sound.js

sound.js

34 ms

lightbox.css

lightbox.css

89 ms

social_share_button.png

social_share_button.png

22 ms

108455149176944.1491.1807697588.png

108455149176944.1491.1807697588.png

213 ms

banniere-diglee-blog-bd.jpg

banniere-diglee-blog-bd.jpg

364 ms

angouleme-1.gif

angouleme-1.gif

430 ms

angouleme-2.gif

angouleme-2.gif

473 ms

angouleme-3.gif

angouleme-3.gif

406 ms

angouleme-4.gif

angouleme-4.gif

593 ms

angouleme-5.gif

angouleme-5.gif

337 ms

angouleme-5-2.gif

angouleme-5-2.gif

499 ms

angouleme-6.gif

angouleme-6.gif

661 ms

angouleme-7.gif

angouleme-7.gif

574 ms

12507353_1670964073159901_2928648494411908234_n.jpg

12507353_1670964073159901_2928648494411908234_n.jpg

514 ms

tumblr.png

tumblr.png

548 ms

email.png

email.png

591 ms

diglee-bienvenue-blog.gif

diglee-bienvenue-blog.gif

604 ms

dedicaces-copie-diglee-blog1.gif

dedicaces-copie-diglee-blog1.gif

628 ms

diglee-coffret-cartes.png

diglee-coffret-cartes.png

648 ms

agenda-diglee-2014-20151.jpg

agenda-diglee-2014-20151.jpg

760 ms

forever-bitch-diglee.png

forever-bitch-diglee.png

941 ms

agenda-cover-2013.gif

agenda-cover-2013.gif

769 ms

diglee-confessions-dune-glitter-addict-light.gif

diglee-confessions-dune-glitter-addict-light.gif

782 ms

couv-diglee-light.gif

couv-diglee-light.gif

757 ms

couv-agendaLIGHT.gif

couv-agendaLIGHT.gif

756 ms

analytics.js

analytics.js

25 ms

amzn_ads.js

amzn_ads.js

16 ms

glamadapt_jsrv.act

glamadapt_jsrv.act

256 ms

quant.js

quant.js

9 ms

beacon.js

beacon.js

7 ms

glam_comscore.js

glam_comscore.js

7 ms

bid

bid

36 ms

collect

collect

17 ms

collect

collect

58 ms

ga-audiences

ga-audiences

34 ms

core.js

core.js

50 ms

metrics_lib.v2.13.js

metrics_lib.v2.13.js

45 ms

9707.js

9707.js

75 ms

cTagsImgCmd.act

cTagsImgCmd.act

10 ms

14555

14555

25 ms

jsadimp.gif

jsadimp.gif

6 ms

clear.gif

clear.gif

6 ms

sync

sync

19 ms

ads.jsonp

ads.jsonp

172 ms

log.act

log.act

72 ms

14555

14555

32 ms

lgl.html

lgl.html

12 ms

log.act

log.act

84 ms

clear.gif

clear.gif

10 ms

pixel;r=152294903;a=p-874AVp33Bbtkg;labels=Style;fpan=1;fpa=P0-392539197-1456764569896;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456764569896;tzo=-180;ref=;url=http%3A%2F%2Fdiglee.com%2F;ogl=

pixel;r=152294903;a=p-874AVp33Bbtkg;labels=Style;fpan=1;fpa=P0-392539197-1456764569896;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456764569896;tzo=-180;ref=;url=http%3A%2F%2Fdiglee.com%2F;ogl=

12 ms

ico-rss.png

ico-rss.png

274 ms

lgrt

lgrt

30 ms

require.js

require.js

30 ms

glamadapt_jsrv.act

glamadapt_jsrv.act

208 ms

blank.gif

blank.gif

53 ms

blank.gif

blank.gif

65 ms

jquery.min.js

jquery.min.js

33 ms

social_iconbox.css

social_iconbox.css

11 ms

qbqsmreEsMDrobsBjGqecXZ3uV-ygokYp4hRBF1FJwVzx2cRSkDfnmbLJJzzUM3gaT09COQLoCITuuoboelCIg=s10

qbqsmreEsMDrobsBjGqecXZ3uV-ygokYp4hRBF1FJwVzx2cRSkDfnmbLJJzzUM3gaT09COQLoCITuuoboelCIg=s10

17 ms

lZtB1sKxWkxrZ1-kDJmQrngFUspnRVaqhPK3P_r4kbzF1yhQ0OWTyAkNkJeo1NihU_SUvRhCmy0i1ELulQ8=s10

lZtB1sKxWkxrZ1-kDJmQrngFUspnRVaqhPK3P_r4kbzF1yhQ0OWTyAkNkJeo1NihU_SUvRhCmy0i1ELulQ8=s10

20 ms

iconbox_18.png

iconbox_18.png

25 ms

log.act

log.act

128 ms

vast-client.js

vast-client.js

27 ms

mediaelement.js

mediaelement.js

25 ms

blocker.js

blocker.js

45 ms

scrollbar.js

scrollbar.js

45 ms

mode_video_json.act

mode_video_json.act

117 ms

alert-overlay.png

alert-overlay.png

112 ms

clear.gif

clear.gif

17 ms

ga.js

ga.js

17 ms

__utm.gif

__utm.gif

59 ms

blank.gif

blank.gif

49 ms

137 ms

animator.js

animator.js

37 ms

flashmanipulation.js

flashmanipulation.js

40 ms

domready.js

domready.js

37 ms

836.jpg

836.jpg

112 ms

840.jpg

840.jpg

110 ms

842.jpg

842.jpg

112 ms

110.jpg

110.jpg

43 ms

816.jpg

816.jpg

144 ms

xd_arbiter.php

xd_arbiter.php

29 ms

xd_arbiter.php

xd_arbiter.php

35 ms

ping

ping

177 ms

def_vw_img_spr.png

def_vw_img_spr.png

56 ms

collect

collect

16 ms

collect

collect

15 ms

glamadapt_psrv.act

glamadapt_psrv.act

453 ms

ga-audiences

ga-audiences

20 ms

like.php

like.php

135 ms

share_button.php

share_button.php

85 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

30 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

14 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

17 ms

clear.gif

clear.gif

4 ms

Accessibility Review

diglee.com accessibility score

86

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.

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

Form elements do not have associated labels

Best Practices

diglee.com best practices score

83

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

diglee.com SEO score

86

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diglee.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Diglee.com 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

diglee.com

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