Tools & Wizards About Us
metaworks.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

metaworks.jp

自動組版ソフトウェア ROCOCO METAWORKS

Page Load Speed

2.8 sec in total

First Response

687 ms

Resources Loaded

2 sec

Page Rendered

135 ms

metaworks.jp screenshot

About Website

Welcome to metaworks.jp homepage info - get ready to check METAWORKS best content for Japan right away, or after learning these important things about metaworks.jp

METAWORKSは膨大な情報を扱う印刷物、データベースとの連動が必要な印刷物の制作を自動化するAdobe InDesign対応の自動組版ソフトウェア

Visit metaworks.jp

Key Findings

We analyzed Metaworks.jp page load time and found that the first response time was 687 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

metaworks.jp performance score

0

Network Requests Diagram

metaworks.jp

687 ms

style.css

320 ms

si.js

46 ms

urchin.js

8 ms

analytics.js

16 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 61% of them (20 requests) were addressed to the original Metaworks.jp, 18% (6 requests) were made to Google-analytics.com and 6% (2 requests) were made to Smarticon.geotrust.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Metaworks.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.5 kB (16%)

Content Size

300.1 kB

After Optimization

252.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 27.8 kB

  • Original 36.6 kB
  • After minification 35.1 kB
  • After compression 8.8 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 27.8 kB or 76% of the original size.

Image Optimization

-5%

Potential reduce by 10.9 kB

  • Original 209.1 kB
  • After minification 198.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. METAWORKS images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.1 kB

  • Original 45.0 kB
  • After minification 45.0 kB
  • After compression 44.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. This website has mostly compressed JavaScripts.

CSS Optimization

-82%

Potential reduce by 7.7 kB

  • Original 9.4 kB
  • After minification 7.9 kB
  • After compression 1.7 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. Metaworks.jp needs all CSS files to be minified and compressed as it can save up to 7.7 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

metaworks.jp

metaworks.jp

687 ms

style.css

style.css

320 ms

si.js

si.js

46 ms

urchin.js

urchin.js

8 ms

analytics.js

analytics.js

16 ms

top_bg.jpg

top_bg.jpg

1135 ms

sp.gif

sp.gif

199 ms

spacer.gif

spacer.gif

325 ms

top_ttnews.gif

top_ttnews.gif

336 ms

top_bn1.jpg

top_bn1.jpg

667 ms

top_bn2.jpg

top_bn2.jpg

710 ms

top_top1.gif

top_top1.gif

359 ms

top_top2.gif

top_top2.gif

483 ms

t_top2.gif

t_top2.gif

502 ms

top_ft.gif

top_ft.gif

535 ms

top_w02.gif

top_w02.gif

642 ms

top_w03.gif

top_w03.gif

669 ms

top_w04.gif

top_w04.gif

712 ms

top_tt_eve.gif

top_tt_eve.gif

803 ms

K20000972_02.gif

K20000972_02.gif

831 ms

sdk.js

sdk.js

164 ms

bk.gif

bk.gif

826 ms

t_bk1.gif

t_bk1.gif

875 ms

t_bk2.gif

t_bk2.gif

880 ms

smarticon

smarticon

79 ms

collect

collect

19 ms

__utm.gif

__utm.gif

6 ms

ga.js

ga.js

13 ms

collect

collect

80 ms

__utm.gif

__utm.gif

36 ms

27 ms

xd_arbiter.php

xd_arbiter.php

141 ms

xd_arbiter.php

xd_arbiter.php

261 ms

SEO Factors

metaworks.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Metaworks.jp 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 Metaworks.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

metaworks.jp

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