Tools & Wizards About Us
blog.elephantcube.com screenshot

Report Summary

  • 92

    Performance

    Renders faster than
    92% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

blog.elephantcube.com

ElephantCube 象盒子

Page Load Speed

2.7 sec in total

First Response

528 ms

Resources Loaded

1.4 sec

Page Rendered

791 ms

blog.elephantcube.com screenshot

About Website

Visit blog.elephantcube.com now to see the best up-to-date Blog Elephant Cube content and also check out these interesting facts you probably never knew about blog.elephantcube.com

給孩子一個歡樂的學習童年

Visit blog.elephantcube.com

Key Findings

We analyzed Blog.elephantcube.com page load time and found that the first response time was 528 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

blog.elephantcube.com performance score

92

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

blog.elephantcube.com

528 ms

107 ms

css

133 ms

125 ms

103 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Blog.elephantcube.com, 20% (19 requests) were made to Pixel.wp.com and 11% (10 requests) were made to Tw.elephantcube.com. The less responsive or slowest element that took the longest time to load (528 ms) belongs to the original domain Blog.elephantcube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.6 kB (51%)

Content Size

997.4 kB

After Optimization

492.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 70.1 kB

  • Original 88.0 kB
  • After minification 86.0 kB
  • After compression 17.9 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 70.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 11.9 kB

  • Original 341.9 kB
  • After minification 329.9 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. Blog Elephant Cube images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 409.9 kB

  • Original 547.3 kB
  • After minification 429.3 kB
  • After compression 137.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 409.9 kB or 75% of the original size.

CSS Optimization

-62%

Potential reduce by 12.6 kB

  • Original 20.2 kB
  • After minification 18.3 kB
  • After compression 7.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. Blog.elephantcube.com needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 62% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (65%)

Requests Now

79

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Elephant Cube. 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 from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

blog.elephantcube.com

blog.elephantcube.com

528 ms

107 ms

css

css

133 ms

125 ms

103 ms

120 ms

115 ms

style.css

style.css

104 ms

gprofiles.js

gprofiles.js

114 ms

wpgroho.js

wpgroho.js

107 ms

112 ms

112 ms

tiled-gallery.css

tiled-gallery.css

116 ms

124 ms

widgets.js

widgets.js

86 ms

116 ms

725X1342.skimlinks.js

725X1342.skimlinks.js

83 ms

w.js

w.js

83 ms

merriweather.css

merriweather.css

24 ms

collage-80.jpg

collage-80.jpg

306 ms

16-3-door-ajar-jar.jpg

16-3-door-ajar-jar.jpg

396 ms

ElephantCube-registered-mark.jpg

ElephantCube-registered-mark.jpg

390 ms

sdk.js

sdk.js

304 ms

orange-small.png

orange-small.png

284 ms

loading.gif

loading.gif

279 ms

16-3-lights-dark.jpg

16-3-lights-dark.jpg

286 ms

16-3-ion-tion-sion-ssion-suffix-noun.jpg

16-3-ion-tion-sion-ssion-suffix-noun.jpg

287 ms

16-3-ble-able-ible-suffix.jpg

16-3-ble-able-ible-suffix.jpg

309 ms

16-3-hole.jpg

16-3-hole.jpg

417 ms

16-3-pig-pen.jpg

16-3-pig-pen.jpg

462 ms

16-3-king-crown-dentist.jpg

16-3-king-crown-dentist.jpg

419 ms

16-3-turmeric.jpg

16-3-turmeric.jpg

418 ms

16-3-turmeric-2.jpg

16-3-turmeric-2.jpg

417 ms

16-3-turmeric-3.jpg

16-3-turmeric-3.jpg

418 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

266 ms

BTu4SsVveqk58cdYjlaM9g.ttf

BTu4SsVveqk58cdYjlaM9g.ttf

284 ms

zpv3sOKAbMf4wff105oLjw.ttf

zpv3sOKAbMf4wff105oLjw.ttf

283 ms

5pEc4QKTMA2oB4Hi9NkS4w.ttf

5pEc4QKTMA2oB4Hi9NkS4w.ttf

307 ms

Genericons.svg

Genericons.svg

161 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

158 ms

XNVd6tsqi9wmKNvnh5HNEKCWcynf_cDxXwCLxiixG1c.ttf

XNVd6tsqi9wmKNvnh5HNEKCWcynf_cDxXwCLxiixG1c.ttf

306 ms

LgcV55siz7BRNdbO3Huj5g.ttf

LgcV55siz7BRNdbO3Huj5g.ttf

385 ms

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

396 ms

Noticons.svg

Noticons.svg

160 ms

BaABdRAi2AAAA

BaABdRAi2AAAA

157 ms

merriweather-bold-webfont.ttf

merriweather-bold-webfont.ttf

160 ms

merriweather-regular-webfont.ttf

merriweather-regular-webfont.ttf

159 ms

merriweather-light-webfont.ttf

merriweather-light-webfont.ttf

160 ms

px.gif

px.gif

240 ms

253 ms

hovercard.css

hovercard.css

193 ms

services.css

services.css

220 ms

count.json

count.json

335 ms

g.gif

g.gif

178 ms

graph.facebook.com

graph.facebook.com

333 ms

count.json

count.json

331 ms

graph.facebook.com

graph.facebook.com

381 ms

count.json

count.json

331 ms

graph.facebook.com

graph.facebook.com

401 ms

count.json

count.json

327 ms

graph.facebook.com

graph.facebook.com

398 ms

count.json

count.json

326 ms

graph.facebook.com

graph.facebook.com

395 ms

count.json

count.json

324 ms

graph.facebook.com

graph.facebook.com

392 ms

count.json

count.json

364 ms

graph.facebook.com

graph.facebook.com

392 ms

count.json

count.json

362 ms

graph.facebook.com

graph.facebook.com

442 ms

collage-80.jpg

collage-80.jpg

311 ms

g.gif

g.gif

108 ms

g.gif

g.gif

108 ms

g.gif

g.gif

109 ms

g.gif

g.gif

114 ms

g.gif

g.gif

113 ms

g.gif

g.gif

131 ms

g.gif

g.gif

131 ms

g.gif

g.gif

131 ms

g.gif

g.gif

131 ms

g.gif

g.gif

153 ms

g.gif

g.gif

133 ms

g.gif

g.gif

232 ms

g.gif

g.gif

231 ms

g.gif

g.gif

231 ms

g.gif

g.gif

231 ms

px.gif

px.gif

110 ms

g.gif

g.gif

170 ms

g.gif

g.gif

169 ms

g.gif

g.gif

187 ms

global-print.css

global-print.css

50 ms

225 ms

xd_arbiter.php

xd_arbiter.php

176 ms

xd_arbiter.php

xd_arbiter.php

273 ms

Accessibility Review

blog.elephantcube.com accessibility score

65

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

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

blog.elephantcube.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

SEO Factors

blog.elephantcube.com SEO score

99

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

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

blog.elephantcube.com

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