Tools & Wizards About Us
writebooks.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

writebooks.jp

Writebooks（ライトブックス）｜電子書籍･デジタルカタログ生成ツール。iPadやiPhone、Androidアプリ対応のSaaS型電子書籍作成システムです。

Page Load Speed

7.3 sec in total

First Response

516 ms

Resources Loaded

6.6 sec

Page Rendered

194 ms

writebooks.jp screenshot

About Website

Visit writebooks.jp now to see the best up-to-date Writebooks content and also check out these interesting facts you probably never knew about writebooks.jp

電子書籍の作成(オーサリング)・販売なら「ライトブックス」。iPhone・iPad・Andoridにも対応した電子書籍・電子カタログのオーサリングツールです。御社も出版社となって、電子書籍・電子カタログの販売が可能です。

Visit writebooks.jp

Key Findings

We analyzed Writebooks.jp page load time and found that the first response time was 516 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

writebooks.jp performance score

0

Network Requests Diagram

writebooks.jp

516 ms

www.writebooks.jp

909 ms

AdLantisLoader.js

1341 ms

jquery-1.3.2.min.js

1132 ms

jquery.easing.1.3.js

583 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 63% of them (45 requests) were addressed to the original Writebooks.jp, 11% (8 requests) were made to Ad.adlantis.jp and 6% (4 requests) were made to Conf.log-marketing.jp. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Writebooks.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 317.2 kB (28%)

Content Size

1.1 MB

After Optimization

805.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Writebooks.jp main page is 1.1 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. 20% of websites need less resources to load. Images take 724.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.9 kB

  • Original 22.4 kB
  • After minification 20.2 kB
  • After compression 5.5 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 16.9 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 25.0 kB

  • Original 724.2 kB
  • After minification 699.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. Writebooks images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 248.1 kB

  • Original 342.0 kB
  • After minification 279.1 kB
  • After compression 94.0 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 248.1 kB or 73% of the original size.

CSS Optimization

-79%

Potential reduce by 27.3 kB

  • Original 34.5 kB
  • After minification 28.1 kB
  • After compression 7.2 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. Writebooks.jp needs all CSS files to be minified and compressed as it can save up to 27.3 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

writebooks.jp

writebooks.jp

516 ms

www.writebooks.jp

www.writebooks.jp

909 ms

AdLantisLoader.js

AdLantisLoader.js

1341 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

1132 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

583 ms

jquery.corner.js

jquery.corner.js

593 ms

jquery.lightbox-0.5.min.js

jquery.lightbox-0.5.min.js

604 ms

jquery.page-scroller-306.js

jquery.page-scroller-306.js

404 ms

jquery.qtip-1.0.0-rc3.js

jquery.qtip-1.0.0-rc3.js

1503 ms

common.js

common.js

783 ms

loader.css

loader.css

943 ms

load_ad

load_ad

365 ms

load_ad

load_ad

382 ms

widget.js

widget.js

57 ms

load_ad

load_ad

369 ms

load_ad

load_ad

378 ms

year.js

year.js

594 ms

basic.css

basic.css

373 ms

module.css

module.css

540 ms

layout.css

layout.css

556 ms

color.css

color.css

370 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

374 ms

Conf_yokota.js

Conf_yokota.js

650 ms

logo.png

logo.png

531 ms

arw_hlnk.png

arw_hlnk.png

370 ms

btn_nav_top.png

btn_nav_top.png

385 ms

nav.png

nav.png

387 ms

arw_nav.png

arw_nav.png

391 ms

arw_nav_c.png

arw_nav_c.png

389 ms

btn_demo.png

btn_demo.png

929 ms

demo_01.png

demo_01.png

1812 ms

case_01.png

case_01.png

1119 ms

case_02.png

case_02.png

947 ms

case_04.png

case_04.png

1139 ms

case_05.png

case_05.png

1061 ms

igm.jpg

igm.jpg

1507 ms

freshers.jpg

freshers.jpg

1508 ms

apps_01

apps_01

1744 ms

apps_02.png

apps_02.png

1861 ms

apps_04.png

apps_04.png

1900 ms

apps_05.png

apps_05.png

2215 ms

arw_detail.png

arw_detail.png

1868 ms

btn_contact.png

btn_contact.png

2139 ms

btn_order.png

btn_order.png

2166 ms

arw_detail_02.png

arw_detail_02.png

2222 ms

footer_logo.png

footer_logo.png

2436 ms

sr.gif

sr.gif

504 ms

show

show

191 ms

show

show

386 ms

top_image.png

top_image.png

3372 ms

bg_h2.png

bg_h2.png

2499 ms

arw_lnk.png

arw_lnk.png

2509 ms

show

show

385 ms

show

show

403 ms

bg_footer.png

bg_footer.png

2565 ms

arw_flnk_fst.png

arw_flnk_fst.png

2576 ms

arw_flnk_snd.png

arw_flnk_snd.png

2801 ms

ga.js

ga.js

7 ms

adlantis.www.js

adlantis.www.js

180 ms

swfobject.js

swfobject.js

359 ms

__utm.gif

__utm.gif

11 ms

ef0adc07d1fb49a8c4a53c11c051480f7274b87b.png

ef0adc07d1fb49a8c4a53c11c051480f7274b87b.png

1805 ms

ef0adc07d1fb49a8c4a53c11c051480f7274b87b.png

ef0adc07d1fb49a8c4a53c11c051480f7274b87b.png

1569 ms

630155f853bb898206c6d260ae92d62b73bd17d1.png

630155f853bb898206c6d260ae92d62b73bd17d1.png

1655 ms

630155f853bb898206c6d260ae92d62b73bd17d1.png

630155f853bb898206c6d260ae92d62b73bd17d1.png

1632 ms

[sr].gif

[sr].gif

490 ms

emd_pt.js

emd_pt.js

536 ms

HTTP_s.js

HTTP_s.js

794 ms

st.php

st.php

378 ms

sst.php

sst.php

345 ms

log_run.php

log_run.php

346 ms

SEO Factors

writebooks.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

writebooks.jp

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