Tools & Wizards About Us
hotmobily.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hotmobily.jp

オリジナルグッズ・ノベルティを小ロット短納期で製作。ホットモバイリーオリジナルグッズ

Page Load Speed

8.1 sec in total

First Response

592 ms

Resources Loaded

6.5 sec

Page Rendered

982 ms

hotmobily.jp screenshot

About Website

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

ホットモバイリーオリジナルグッズ。小ロットもOKで短納期。ラバーストラップやラバーコースターの製作を中心に、社名やロゴが印刷できる、オリジナルのグッズ、販促品を製造しております。同人や学校の記念品として、個人のお客様もご注文頂けます。

Visit hotmobily.jp

Key Findings

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

Performance Metrics

hotmobily.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value12,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.103

89/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

hotmobily.jp

592 ms

hotmobily.jp

1666 ms

fonts.css

493 ms

base4.css

538 ms

header.css

536 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 95% of them (84 requests) were addressed to the original Hotmobily.jp, 2% (2 requests) were made to Googletagmanager.com and 1% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Hotmobily.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 496.6 kB (75%)

Content Size

662.3 kB

After Optimization

165.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotmobily.jp main page is 662.3 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. Javascripts take 442.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 107.5 kB

  • Original 128.9 kB
  • After minification 115.9 kB
  • After compression 21.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 107.5 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.4 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.

JavaScript Optimization

-71%

Potential reduce by 316.6 kB

  • Original 442.9 kB
  • After minification 437.0 kB
  • After compression 126.3 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 316.6 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 72.5 kB

  • Original 87.1 kB
  • After minification 68.4 kB
  • After compression 14.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. Hotmobily.jp needs all CSS files to be minified and compressed as it can save up to 72.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotmobily.jp

hotmobily.jp

592 ms

hotmobily.jp

hotmobily.jp

1666 ms

fonts.css

fonts.css

493 ms

base4.css

base4.css

538 ms

header.css

header.css

536 ms

nav.css

nav.css

565 ms

sidemenu.css

sidemenu.css

564 ms

design3.css

design3.css

659 ms

footer.css

footer.css

716 ms

colorbox.css

colorbox.css

715 ms

jquery.min.js

jquery.min.js

945 ms

sidemenu.js

sidemenu.js

751 ms

banner_style.css

banner_style.css

752 ms

mbmenu_customs.css

mbmenu_customs.css

824 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

1071 ms

jquery.mmenu.min.all.js

jquery.mmenu.min.all.js

1071 ms

jquery-ui.min.js

jquery-ui.min.js

2054 ms

tinyscrollbar_2nd.css

tinyscrollbar_2nd.css

941 ms

reviews.css

reviews.css

990 ms

jquery.bxslider.css

jquery.bxslider.css

1130 ms

coin-slider.min.js

coin-slider.min.js

1135 ms

coin-slider-styles.css

coin-slider-styles.css

1155 ms

ism-2.2.min.js

ism-2.2.min.js

1250 ms

jquery.tinyscrollbar.js

jquery.tinyscrollbar.js

1248 ms

widgets.js

widgets.js

16 ms

fontplus.js

fontplus.js

1010 ms

js

js

52 ms

js

js

107 ms

jquery.bxslider.js

jquery.bxslider.js

757 ms

new_2023.webp

new_2023.webp

1138 ms

contact-2021-test.webp

contact-2021-test.webp

443 ms

jp.webp

jp.webp

444 ms

us.webp

us.webp

445 ms

cn.webp

cn.webp

446 ms

kr.webp

kr.webp

445 ms

th.webp

th.webp

447 ms

jp.png

jp.png

448 ms

hm_logo_navbar.webp

hm_logo_navbar.webp

448 ms

smenu04.webp

smenu04.webp

448 ms

04.webp

04.webp

448 ms

35x35-strap.webp

35x35-strap.webp

517 ms

rubber-keyhold-s.webp

rubber-keyhold-s.webp

555 ms

smenu03.webp

smenu03.webp

556 ms

smenu22.webp

smenu22.webp

567 ms

smenu22_2.webp

smenu22_2.webp

567 ms

smenu11.webp

smenu11.webp

668 ms

smenu33.webp

smenu33.webp

740 ms

smenu30.webp

smenu30.webp

740 ms

smenu06.webp

smenu06.webp

753 ms

smenu22.webp

smenu22.webp

753 ms

smenu14.webp

smenu14.webp

825 ms

Twitter-icon.webp

Twitter-icon.webp

886 ms

Facebook-icon.webp

Facebook-icon.webp

894 ms

Youtube-icon.webp

Youtube-icon.webp

941 ms

IG_icon.webp

IG_icon.webp

942 ms

btn_sample02_new.webp

btn_sample02_new.webp

1153 ms

btn_meetingdate_new.webp

btn_meetingdate_new.webp

1238 ms

blog_content_button.webp

blog_content_button.webp

1425 ms

banner-rubber-height.webp

banner-rubber-height.webp

1316 ms

banner-rubber-coating.webp

banner-rubber-coating.webp

1873 ms

rubber-strap.webp

rubber-strap.webp

1327 ms

rubber-keyholder.webp

rubber-keyholder.webp

1318 ms

rubber-coaster.webp

rubber-coaster.webp

1416 ms

acrylic-keyholder.webp

acrylic-keyholder.webp

1503 ms

acrylic-figure.webp

acrylic-figure.webp

1485 ms

acrylic-phonestand.webp

acrylic-phonestand.webp

1078 ms

acrylic-umbrella.webp

acrylic-umbrella.webp

1152 ms

acrylic-badge.webp

acrylic-badge.webp

1163 ms

acrylic-coaster.webp

acrylic-coaster.webp

1209 ms

acrylic-hairbunch.webp

acrylic-hairbunch.webp

1249 ms

acrylic-griptok.webp

acrylic-griptok.webp

2256 ms

button_gotop.webp

button_gotop.webp

1327 ms

getLang

getLang

1512 ms

jp.webp

jp.webp

1363 ms

us.webp

us.webp

1429 ms

cn.webp

cn.webp

1432 ms

kr.webp

kr.webp

1428 ms

th.webp

th.webp

1499 ms

hm_logo_navbar.webp

hm_logo_navbar.webp

1505 ms

smenu04.webp

smenu04.webp

1487 ms

04.webp

04.webp

1456 ms

index.php

index.php

1409 ms

get_review.php

get_review.php

1649 ms

35x35-strap.webp

35x35-strap.webp

1508 ms

s_banner_hotstrap_sq.webp

s_banner_hotstrap_sq.webp

1553 ms

arrow_icon.webp

arrow_icon.webp

1500 ms

237 ms

bx_loader.gif

bx_loader.gif

167 ms

Accessibility Review

hotmobily.jp accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

hotmobily.jp best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hotmobily.jp SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

    N/A

  • Encoding

    UTF-8

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

hotmobily.jp

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