Tools & Wizards About Us
mox-motion.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

mox-motion.com

株式会社モックス｜3DCGアニメーションを手付けモーションでより魅力的に。

Page Load Speed

4.6 sec in total

First Response

505 ms

Resources Loaded

3.7 sec

Page Rendered

452 ms

mox-motion.com screenshot

About Website

Visit mox-motion.com now to see the best up-to-date Mox Motion content for Japan and also check out these interesting facts you probably never knew about mox-motion.com

モックスは2007年の設立以来、3DCG制作工程のうちキャラクターアニメーションとモーションキャプチャー編集を専門で行う3Dアニメーション制作会社です。

Visit mox-motion.com

Key Findings

We analyzed Mox-motion.com page load time and found that the first response time was 505 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

mox-motion.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

mox-motion.com

505 ms

mox-motion.com

1095 ms

js

42 ms

style.min.css

707 ms

block.css

495 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 58% of them (36 requests) were addressed to the original Mox-motion.com, 29% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mox-motion.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.7 kB (25%)

Content Size

880.6 kB

After Optimization

661.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 28.5 kB

  • Original 35.8 kB
  • After minification 33.2 kB
  • After compression 7.4 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 28.5 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 9.6 kB

  • Original 613.4 kB
  • After minification 603.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. Mox Motion images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 55.7 kB

  • Original 84.4 kB
  • After minification 84.2 kB
  • After compression 28.8 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 55.7 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 124.9 kB

  • Original 146.9 kB
  • After minification 139.4 kB
  • After compression 22.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. Mox-motion.com needs all CSS files to be minified and compressed as it can save up to 124.9 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

58

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mox-motion.com

mox-motion.com

505 ms

mox-motion.com

mox-motion.com

1095 ms

js

js

42 ms

style.min.css

style.min.css

707 ms

block.css

block.css

495 ms

styles.css

styles.css

529 ms

pagenavi-css.css

pagenavi-css.css

538 ms

wpp.css

wpp.css

566 ms

common.css

common.css

760 ms

top.css

top.css

658 ms

wpp.min.js

wpp.min.js

540 ms

widgets.js

widgets.js

94 ms

index.js

index.js

546 ms

index.js

index.js

587 ms

api.js

api.js

39 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

660 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

712 ms

wp-polyfill.min.js

wp-polyfill.min.js

886 ms

index.js

index.js

724 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

19 ms

common.js

common.js

775 ms

css

css

34 ms

logo-mox.svg

logo-mox.svg

1183 ms

ico-search.svg

ico-search.svg

212 ms

20230515_202434-e1718248112515.jpg

20230515_202434-e1718248112515.jpg

1459 ms

1683014397262-e1717572981764.jpg

1683014397262-e1717572981764.jpg

477 ms

20230421_015810-e1716865212415.jpg

20230421_015810-e1716865212415.jpg

560 ms

20230415_131456.jpg

20230415_131456.jpg

697 ms

20230412_222406-e1715222867295.jpg

20230412_222406-e1715222867295.jpg

642 ms

20230409_214640-e1713946904377.jpg

20230409_214640-e1713946904377.jpg

660 ms

20230405_204151-e1713405665623.jpg

20230405_204151-e1713405665623.jpg

747 ms

20230330_010655-e1712723963429.jpg

20230330_010655-e1712723963429.jpg

987 ms

20230315_161726.jpg

20230315_161726.jpg

1011 ms

20230309_230140-e1711415087281.jpg

20230309_230140-e1711415087281.jpg

860 ms

20230302_204659-1.jpg

20230302_204659-1.jpg

934 ms

20230302_204659.jpg

20230302_204659.jpg

1025 ms

20230225_220731-e1710122795569.jpg

20230225_220731-e1710122795569.jpg

1126 ms

img-footer-company.jpg

img-footer-company.jpg

1165 ms

img-footer-service.png

img-footer-service.png

1191 ms

ico-twitter.svg

ico-twitter.svg

1189 ms

ico-youotube.svg

ico-youotube.svg

1316 ms

HTx3L3I-JCGChYJ8VI-L6OO_au7B6xHT3A.woff

HTx3L3I-JCGChYJ8VI-L6OO_au7B6xHT3A.woff

28 ms

HTxwL3I-JCGChYJ8VI-L6OO_au7B4873z3bWvw.woff

HTxwL3I-JCGChYJ8VI-L6OO_au7B4873z3bWvw.woff

43 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

56 ms

settings

settings

71 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

22 ms

MoxMotion

MoxMotion

65 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

49 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

72 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

79 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

103 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

107 ms

_buildManifest.js

_buildManifest.js

116 ms

_ssgManifest.js

_ssgManifest.js

116 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

20 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

22 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

41 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

49 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

66 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

26 ms

Accessibility Review

mox-motion.com accessibility score

96

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.

Best Practices

mox-motion.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mox-motion.com SEO score

93

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

Links do not have descriptive text

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mox-motion.com 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 Mox-motion.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

mox-motion.com

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