Tools & Wizards About Us
drollify.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

drollify.com

Loading...

Page Load Speed

9.7 sec in total

First Response

1.1 sec

Resources Loaded

8.1 sec

Page Rendered

516 ms

drollify.com screenshot

About Website

Click here to check amazing Drollify content for Brazil. Otherwise, check out these important facts you probably never knew about drollify.com

Stories on the net

Visit drollify.com

Key Findings

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

Performance Metrics

drollify.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

www.drollify.com

1073 ms

wp-emoji-release.min.js

93 ms

wbounce.min.css

110 ms

styles.min.css

111 ms

style.css

112 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 29% of them (21 requests) were addressed to the original Drollify.com, 8% (6 requests) were made to D3dytsf4vrjn5x.cloudfront.net and 7% (5 requests) were made to I2.wp.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Drollify.com.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

770.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 104.1 kB

  • Original 137.2 kB
  • After minification 128.9 kB
  • After compression 33.1 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 104.1 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 3.9 kB

  • Original 476.2 kB
  • After minification 472.3 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. Drollify images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 162.4 kB

  • Original 327.8 kB
  • After minification 321.9 kB
  • After compression 165.4 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 162.4 kB or 50% of the original size.

CSS Optimization

-75%

Potential reduce by 291.6 kB

  • Original 390.9 kB
  • After minification 373.4 kB
  • After compression 99.3 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. Drollify.com needs all CSS files to be minified and compressed as it can save up to 291.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (49%)

Requests Now

67

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.drollify.com

www.drollify.com

1073 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

93 ms

wbounce.min.css

wbounce.min.css

110 ms

styles.min.css

styles.min.css

111 ms

style.css

style.css

112 ms

font-awesome.min.css

font-awesome.min.css

120 ms

responsive.css

responsive.css

122 ms

jetpack.css

jetpack.css

148 ms

jquery.js

jquery.js

256 ms

jquery-migrate.min.js

jquery-migrate.min.js

165 ms

q2w3-fixed-widget.min.js

q2w3-fixed-widget.min.js

166 ms

customscript.js

customscript.js

172 ms

popup.js

popup.js

171 ms

css

css

36 ms

adsbygoogle.js

adsbygoogle.js

8 ms

page.js

page.js

15 ms

photon.js

photon.js

177 ms

wbounce.min.js

wbounce.min.js

190 ms

devicepx-jetpack.js

devicepx-jetpack.js

57 ms

script.min.js

script.min.js

190 ms

sticky.js

sticky.js

200 ms

ajax.js

ajax.js

203 ms

history.js

history.js

345 ms

e-201609.js

e-201609.js

4 ms

sdk.js

sdk.js

92 ms

black-bananas.jpg

black-bananas.jpg

82 ms

18th-bday-og.jpg

18th-bday-og.jpg

78 ms

mom-looks-at-son-og.jpg

mom-looks-at-son-og.jpg

77 ms

love-story-og.jpg

love-story-og.jpg

72 ms

lingerie-mma-og.png

lingerie-mma-og.png

71 ms

craft-room-basement-og.jpg

craft-room-basement-og.jpg

72 ms

giant-blanket-og.png

giant-blanket-og.png

76 ms

neighbors.jpg

neighbors.jpg

72 ms

pattern1.png

pattern1.png

119 ms

random-duet-groban-og.jpg

random-duet-groban-og.jpg

71 ms

hang-og.jpg

hang-og.jpg

70 ms

ca-pub-2046821586447259.js

ca-pub-2046821586447259.js

204 ms

zrt_lookup.html

zrt_lookup.html

260 ms

show_ads_impl.js

show_ads_impl.js

188 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

320 ms

Y9iTUUNz6lbl6TrvV4iws6UezEdMYI9XloeJYXchQao.ttf

Y9iTUUNz6lbl6TrvV4iws6UezEdMYI9XloeJYXchQao.ttf

53 ms

AWM5wXtMJeRP-AcRTgT4qQ.ttf

AWM5wXtMJeRP-AcRTgT4qQ.ttf

173 ms

widget.aspx

widget.aspx

301 ms

251 ms

xd_arbiter.php

xd_arbiter.php

206 ms

xd_arbiter.php

xd_arbiter.php

213 ms

sm13.html

sm13.html

161 ms

ads

ads

317 ms

g.gif

g.gif

46 ms

osd.js

osd.js

24 ms

icons.15.svg.css

icons.15.svg.css

70 ms

ga.js

ga.js

74 ms

like.php

like.php

65 ms

GetWidget.aspx

GetWidget.aspx

163 ms

_i1D6e24ehq.js

_i1D6e24ehq.js

38 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

24 ms

_i1D6e24ehq.js

_i1D6e24ehq.js

12 ms

42dbf461f66f207fa1dee5276c937ff0.jpg

42dbf461f66f207fa1dee5276c937ff0.jpg

8 ms

pixel.gif

pixel.gif

127 ms

c_ad_logo.png

c_ad_logo.png

5 ms

e2d7b3f4580df792a19d36dd4cfb347e.jpg

e2d7b3f4580df792a19d36dd4cfb347e.jpg

4 ms

bf03f148758d91a43f9ed3ee44af0e1d.jpg

bf03f148758d91a43f9ed3ee44af0e1d.jpg

5 ms

49a671eeeca01f0d11323d35548b54c8.jpg

49a671eeeca01f0d11323d35548b54c8.jpg

9 ms

1c2c4c7d3337d56f082d2293a1588c06.jpg

1c2c4c7d3337d56f082d2293a1588c06.jpg

21 ms

fba1b1c9c15e37dfa376a51a459d326f.jpg

fba1b1c9c15e37dfa376a51a459d326f.jpg

9 ms

m_js_controller.js

m_js_controller.js

35 ms

abg.js

abg.js

72 ms

favicon

favicon

67 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

61 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

48 ms

s

s

18 ms

x_button_blue2.png

x_button_blue2.png

5 ms

Accessibility Review

drollify.com accessibility score

85

Accessibility Issues

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

Document doesn't have a <title> element

High

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

Best Practices

drollify.com 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

High

Page has valid source maps

SEO Factors

drollify.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drollify.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Drollify.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

drollify.com

Open Graph data is detected on the main page of Drollify. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: