Tools & Wizards About Us
mixi.jp screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

mixi.jp

ソーシャル・ネットワーキング サービス [mixi(ミクシィ)]

Page Load Speed

4.9 sec in total

First Response

342 ms

Resources Loaded

4.3 sec

Page Rendered

264 ms

mixi.jp screenshot

About Website

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

mixi(ミクシィ)は、日記、写真共有、ゲームや便利ツール満載のアプリなど、さまざまなサービスで友人・知人とのコミュニケーションをさらに便利に楽しくする、日本最大規模のソーシャル・ネットワーキングサービスです。

Visit mixi.jp

Key Findings

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

Performance Metrics

mixi.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value11,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value32.3 s

0/100

10%

Network Requests Diagram

mixi.jp

342 ms

home.pl

898 ms

core-js-3.25.5.js

81 ms

datalist-polyfill-1.24.3.js

768 ms

fetch-3.6.2.js

776 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Mixi.jp, 27% (17 requests) were made to Script.mixi.net and 24% (15 requests) were made to Img.mixi.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Script.mixi.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.3 kB (13%)

Content Size

389.7 kB

After Optimization

337.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mixi.jp main page is 389.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 253.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 35.2 kB

  • Original 45.3 kB
  • After minification 42.8 kB
  • After compression 10.1 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 35.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 498 B

  • Original 82.0 kB
  • After minification 81.5 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. Mixi images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 16.4 kB

  • Original 253.1 kB
  • After minification 252.8 kB
  • After compression 236.7 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

-2%

Potential reduce by 202 B

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 9.1 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. Mixi.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (50%)

Requests Now

58

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mixi.jp

mixi.jp

342 ms

home.pl

home.pl

898 ms

core-js-3.25.5.js

core-js-3.25.5.js

81 ms

datalist-polyfill-1.24.3.js

datalist-polyfill-1.24.3.js

768 ms

fetch-3.6.2.js

fetch-3.6.2.js

776 ms

classList-1.2.20180112.min.js

classList-1.2.20180112.min.js

780 ms

element-remove-1.0.4.js

element-remove-1.0.4.js

774 ms

portal.production.css

portal.production.css

163 ms

mixi-qa-error-report.production.js

mixi-qa-error-report.production.js

784 ms

lodash-underscore-string-4.17.21-2.0.0-compress.js

lodash-underscore-string-4.17.21-2.0.0-compress.js

802 ms

namespace-1.0.1-brook-compress.js

namespace-1.0.1-brook-compress.js

1470 ms

mixi-customized-prototype-effects.js

mixi-customized-prototype-effects.js

1478 ms

disable-double-submit.js

disable-double-submit.js

786 ms

js

js

163 ms

jquery-3.6.0.min-noconflict-compress.js

jquery-3.6.0.min-noconflict-compress.js

1486 ms

co-mixi.production.js

co-mixi.production.js

1725 ms

mixi-model.production.js

mixi-model.production.js

1723 ms

mixi-ui.production.js

mixi-ui.production.js

819 ms

mixi-analysis-.production.js

mixi-analysis-.production.js

813 ms

mixi-adnetwork.production.js

mixi-adnetwork.production.js

1718 ms

mixi-menu.pc.production.js

mixi-menu.pc.production.js

1478 ms

logo_mixi001.svg

logo_mixi001.svg

727 ms

137_20240104_4130950_2_160x160.jpg

137_20240104_4130950_2_160x160.jpg

539 ms

661596_196.jpg

661596_196.jpg

461 ms

137_20240104_4131656_9_160x160.jpg

137_20240104_4131656_9_160x160.jpg

550 ms

photoup001.gif

photoup001.gif

245 ms

990652_9.gif

990652_9.gif

538 ms

1404_22.jpg

1404_22.jpg

475 ms

4138327_72.jpg

4138327_72.jpg

537 ms

77197_247.jpg

77197_247.jpg

474 ms

9_45.gif

9_45.gif

548 ms

6288643_238.jpg

6288643_238.jpg

550 ms

83934_67.jpg

83934_67.jpg

548 ms

4553473_150.jpg

4553473_150.jpg

568 ms

news001.gif

news001.gif

352 ms

arrow001.gif

arrow001.gif

358 ms

list003.gif

list003.gif

394 ms

news_reaction004.gif

news_reaction004.gif

394 ms

news_reaction005.gif

news_reaction005.gif

394 ms

community001.gif

community001.gif

394 ms

mixi001.gif

mixi001.gif

229 ms

community002.gif

community002.gif

262 ms

news003.gif

news003.gif

262 ms

game002.gif

game002.gif

261 ms

word002.gif

word002.gif

261 ms

event002.gif

event002.gif

271 ms

gpt.js

gpt.js

243 ms

mixi.min.js

mixi.min.js

918 ms

apstag.js

apstag.js

195 ms

api.js

api.js

214 ms

recaptcha__en.js

recaptcha__en.js

113 ms

pubads_impl.js

pubads_impl.js

99 ms

pubcid.min.js

pubcid.min.js

58 ms

esp.js

esp.js

82 ms

encrypted-tag-g.js

encrypted-tag-g.js

152 ms

uid2SecureSignal.js

uid2SecureSignal.js

52 ms

sync.min.js

sync.min.js

71 ms

publishertag.ids.js

publishertag.ids.js

61 ms

map

map

131 ms

increment

increment

414 ms

tag

tag

167 ms

latest.json

latest.json

41 ms

Accessibility Review

mixi.jp accessibility score

92

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

Best Practices

mixi.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mixi.jp SEO score

91

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

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

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

mixi.jp

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