Tools & Wizards About Us
greenebook.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

greenebook.com

閣林讀樂網｜親子童書•知識百科•藝術人文•生活旅遊•健康養生

Page Load Speed

3.3 sec in total

First Response

506 ms

Resources Loaded

2.7 sec

Page Rendered

136 ms

greenebook.com screenshot

About Website

Visit greenebook.com now to see the best up-to-date Greenebook content and also check out these interesting facts you probably never knew about greenebook.com

閣林文創成立於1989年，旗下擁有閣林國際圖書、明天國際圖書、京中玉國際圖書等三個品牌，並跨足文創產業，推廣舉辦大型藝術展覽活動。 28年來，閣林文創始終抱持著以出版優質圖書為主旨，出版品包括知識百科、童書、旅遊、生活、文學、歷史、健康養生等，並多次獲得金鼎獎、中小學優良課外讀物推介、好書大家讀等各類獎項肯定。

Visit greenebook.com

Key Findings

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

Performance Metrics

greenebook.com performance score

0

Network Requests Diagram

greenebook.com

506 ms

styles.css

414 ms

jquery-ui-1.8.18.custom.css

462 ms

ui.js

477 ms

jquery.min.js

947 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that all of those requests were addressed to Greenebook.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Greenebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 415.7 kB (61%)

Content Size

677.9 kB

After Optimization

262.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greenebook.com main page is 677.9 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 464.9 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 2.9 kB

  • Original 4.6 kB
  • After minification 4.5 kB
  • After compression 1.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 2.9 kB or 64% of the original size.

Image Optimization

-3%

Potential reduce by 4.1 kB

  • Original 126.3 kB
  • After minification 122.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. Greenebook images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 338.6 kB

  • Original 464.9 kB
  • After minification 447.9 kB
  • After compression 126.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 338.6 kB or 73% of the original size.

CSS Optimization

-85%

Potential reduce by 70.1 kB

  • Original 82.1 kB
  • After minification 66.3 kB
  • After compression 12.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. Greenebook.com needs all CSS files to be minified and compressed as it can save up to 70.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (23%)

Requests Now

22

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

greenebook.com

greenebook.com

506 ms

styles.css

styles.css

414 ms

jquery-ui-1.8.18.custom.css

jquery-ui-1.8.18.custom.css

462 ms

ui.js

ui.js

477 ms

jquery.min.js

jquery.min.js

947 ms

common.js

common.js

499 ms

app.js

app.js

966 ms

jquery-ui-1.8.18.custom.min.js

jquery-ui-1.8.18.custom.min.js

1259 ms

jquery.ui.datepicker-zh-TW.js

jquery.ui.datepicker-zh-TW.js

673 ms

linen.jpg

linen.jpg

248 ms

linen_login.jpg

linen_login.jpg

454 ms

roundcube_logo.png

roundcube_logo.png

465 ms

login_shadow.png

login_shadow.png

248 ms

ajaxloader.gif

ajaxloader.gif

236 ms

buttons.png

buttons.png

646 ms

addcontact.png

addcontact.png

428 ms

filetypes.png

filetypes.png

641 ms

listicons.png

listicons.png

854 ms

messages.png

messages.png

627 ms

quota.png

quota.png

641 ms

selector.png

selector.png

662 ms

splitter.png

splitter.png

827 ms

watermark.jpg

watermark.jpg

845 ms

SEO Factors

greenebook.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenebook.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Greenebook.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

greenebook.com

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