Tools & Wizards About Us
sitemix.jp screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 46

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

sitemix.jp

無料ホームページ　容量無制限【TOK2.com】

Page Load Speed

5.8 sec in total

First Response

1.1 sec

Resources Loaded

4.2 sec

Page Rendered

444 ms

sitemix.jp screenshot

About Website

Click here to check amazing Sitemix content for India. Otherwise, check out these important facts you probably never knew about sitemix.jp

無料ホームページのTOK2は、容量無制限・商用無制限で、PHP・CGI ・FTP・ファイルマネージャーまで使えます。さらに、ブログ感覚でHPができるTOK2 CMSも加わって超お得なホームページポータルサイトです。有料レンタルサーバも充実：月額２００円！

Visit sitemix.jp

Key Findings

We analyzed Sitemix.jp page load time and found that the first response time was 1.1 sec and then it took 4.7 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

sitemix.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value570 ms

52/100

30%

CLS (Cumulative Layout Shift)

Value0.127

82/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

sitemix.jp

1069 ms

import-gl.css

295 ms

import-lc.css

345 ms

import-lc.css

347 ms

import-lc.css

395 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 84% of them (99 requests) were addressed to the original Sitemix.jp, 3% (3 requests) were made to B91.yahoo.co.jp and 2% (2 requests) were made to File.7artisan.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Sitemix.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.0 kB (32%)

Content Size

484.7 kB

After Optimization

331.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 58.3 kB

  • Original 71.5 kB
  • After minification 51.8 kB
  • After compression 13.2 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. This page needs HTML code to be minified as it can gain 19.7 kB, which is 28% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.3 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 14.1 kB

  • Original 276.6 kB
  • After minification 262.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. Sitemix images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 54.9 kB

  • Original 103.3 kB
  • After minification 103.2 kB
  • After compression 48.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 54.9 kB or 53% of the original size.

CSS Optimization

-77%

Potential reduce by 25.7 kB

  • Original 33.3 kB
  • After minification 25.6 kB
  • After compression 7.6 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. Sitemix.jp needs all CSS files to be minified and compressed as it can save up to 25.7 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (41%)

Requests Now

116

After Optimization

69

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sitemix.jp

sitemix.jp

1069 ms

import-gl.css

import-gl.css

295 ms

import-lc.css

import-lc.css

345 ms

import-lc.css

import-lc.css

347 ms

import-lc.css

import-lc.css

395 ms

jquery.js

jquery.js

984 ms

newwindow.js

newwindow.js

438 ms

base.css

base.css

220 ms

fontstyles.css

fontstyles.css

221 ms

classes.css

classes.css

295 ms

navi.css

navi.css

325 ms

global_header.css

global_header.css

289 ms

contents.css

contents.css

343 ms

common.css

common.css

344 ms

layout02.css

layout02.css

386 ms

contents.css

contents.css

441 ms

contents.css

contents.css

424 ms

conversion.js

conversion.js

523 ms

jquery.rss.min.js

jquery.rss.min.js

434 ms

bn_classc.jpg

bn_classc.jpg

639 ms

bn_201511.png

bn_201511.png

642 ms

sm_top.jpg

sm_top.jpg

521 ms

bg.gif

bg.gif

200 ms

header_bg.gif

header_bg.gif

200 ms

logo.gif

logo.gif

173 ms

head_navi01.gif

head_navi01.gif

203 ms

head_navi02.gif

head_navi02.gif

178 ms

head_navi03.gif

head_navi03.gif

154 ms

head_navi04.gif

head_navi04.gif

299 ms

head_navi05.gif

head_navi05.gif

343 ms

logo_sitemix.gif

logo_sitemix.gif

348 ms

contents_bg.gif

contents_bg.gif

395 ms

top_free_title.gif

top_free_title.gif

595 ms

bg_free_top.gif

bg_free_top.gif

396 ms

btn_free.gif

btn_free.gif

444 ms

top_free_service01.gif

top_free_service01.gif

513 ms

top_free_service02.gif

top_free_service02.gif

519 ms

top_free_service03.gif

top_free_service03.gif

592 ms

top_free_service04.gif

top_free_service04.gif

593 ms

top_free_service05.gif

top_free_service05.gif

588 ms

top_free_service06.gif

top_free_service06.gif

684 ms

top_free_freetext.gif

top_free_freetext.gif

689 ms

btn_charge_det-app01.gif

btn_charge_det-app01.gif

734 ms

bg_charge_top.gif

bg_charge_top.gif

788 ms

btn_charge.gif

btn_charge.gif

788 ms

top_charge_service01.gif

top_charge_service01.gif

789 ms

top_charge_service02.gif

top_charge_service02.gif

855 ms

top_charge_service03.gif

top_charge_service03.gif

861 ms

top_charge_service04.gif

top_charge_service04.gif

879 ms

top_charge_service05.gif

top_charge_service05.gif

985 ms

top_charge_service06.gif

top_charge_service06.gif

985 ms

btn_charge_det-app.gif

btn_charge_det-app.gif

987 ms

top_ranking_body.gif

top_ranking_body.gif

1026 ms

top_accessranking_head.gif

top_accessranking_head.gif

1032 ms

icn_ranking.gif

icn_ranking.gif

1025 ms

line01.gif

line01.gif

1181 ms

top_ranking_foot.gif

top_ranking_foot.gif

1182 ms

bn_wp.jpg

bn_wp.jpg

872 ms

sdk.js

sdk.js

270 ms

top_charge_under.gif

top_charge_under.gif

1150 ms

ga.js

ga.js

24 ms

__utm.gif

__utm.gif

24 ms

conversion.js

conversion.js

971 ms

domain_index_h02.gif

domain_index_h02.gif

1022 ms

404.php

404.php

1036 ms

top_domain_bg.gif

top_domain_bg.gif

1033 ms

top_domainmap.gif

top_domainmap.gif

1266 ms

btn_checkdomain02.gif

btn_checkdomain02.gif

1181 ms

top_ssl_title.gif

top_ssl_title.gif

1377 ms

top_ssl_parts01.gif

top_ssl_parts01.gif

1085 ms

157 ms

xd_arbiter.php

xd_arbiter.php

226 ms

xd_arbiter.php

xd_arbiter.php

431 ms

icn01.gif

icn01.gif

1035 ms

btn_ssl.gif

btn_ssl.gif

1031 ms

service_ad.gif

service_ad.gif

1323 ms

top_h02.gif

top_h02.gif

1155 ms

top_sitemix_step.gif

top_sitemix_step.gif

1138 ms

top_ranking_head.gif

top_ranking_head.gif

1070 ms

line_ranking.gif

line_ranking.gif

1091 ms

top_info_body.gif

top_info_body.gif

1133 ms

top_info_head.gif

top_info_head.gif

1183 ms

top_info_foot.gif

top_info_foot.gif

1185 ms

top_pr02.gif

top_pr02.gif

1184 ms

rightside_user_head.gif

rightside_user_head.gif

1072 ms

rightside_login_foot.gif

rightside_login_foot.gif

1201 ms

rightside_newregist_head.gif

rightside_newregist_head.gif

1160 ms

rigteside_btn_newregist.gif

rigteside_btn_newregist.gif

1113 ms

rightside_newregist_foot.gif

rightside_newregist_foot.gif

1185 ms

rightside_login_head.gif

rightside_login_head.gif

1185 ms

rightside_btn_login.gif

rightside_btn_login.gif

1119 ms

rightside_h01.gif

rightside_h01.gif

1201 ms

tok2.gif

tok2.gif

1185 ms

logo_bfit.gif

logo_bfit.gif

1060 ms

BizServelogo77_13.gif

BizServelogo77_13.gif

1181 ms

logo_girlscity.gif

logo_girlscity.gif

1182 ms

logo_m-girlscity.gif

logo_m-girlscity.gif

1146 ms

logo_dan-d.gif

logo_dan-d.gif

1165 ms

logo_sportsfan.gif

logo_sportsfan.gif

1200 ms

879 ms

ScriptServlet

ScriptServlet

75 ms

www.feedrapp.info

www.feedrapp.info

1303 ms

857 ms

logo_carsfan.gif

logo_carsfan.gif

1063 ms

logo_myrecipe.gif

logo_myrecipe.gif

1182 ms

logo_moecity.gif

logo_moecity.gif

1182 ms

logo_topseller.gif

logo_topseller.gif

1182 ms

rightside_h03.gif

rightside_h03.gif

1132 ms

rightside_h02.gif

rightside_h02.gif

1198 ms

like.php

like.php

89 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

496 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

556 ms

bn_support_200.jpg

bn_support_200.jpg

1203 ms

footer_bottom.gif

footer_bottom.gif

1109 ms

rightside_login_body.gif

rightside_login_body.gif

1184 ms

rightside_newregist_body.gif

rightside_newregist_body.gif

1185 ms

footer_line.gif

footer_line.gif

1104 ms

copyright_bg.gif

copyright_bg.gif

1027 ms

Accessibility Review

sitemix.jp accessibility score

46

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.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

sitemix.jp best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

sitemix.jp SEO score

62

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

Image elements do not have [alt] attributes

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 Sitemix.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 Sitemix.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

sitemix.jp

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