Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

jan39.com

雀荘をお探しなら雀サクッ - 人気の激安店・麻雀大会もおまかせ

Page Load Speed

9.5 sec in total

First Response

539 ms

Resources Loaded

8.3 sec

Page Rendered

627 ms

jan39.com screenshot

About Website

Visit jan39.com now to see the best up-to-date Jan 39 content for Japan and also check out these interesting facts you probably never knew about jan39.com

初心者OKのフリー雀荘や麻雀店を掲載している日本最大級の雀荘検索サイトです。お住まいの地域や最寄駅での検索はもちろん、激安店、禁煙雀荘、ノーレート雀荘などの情報も満載です!麻雀大会やイベント、求人情報などコンテンツも充実!

Visit jan39.com

Key Findings

We analyzed Jan39.com page load time and found that the first response time was 539 ms and then it took 9 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

jan39.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value5,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

jan39.com

539 ms

jan39.com

1299 ms

gtm.js

75 ms

adsbygoogle.js

143 ms

compass.js

810 ms

Our browser made a total of 247 requests to load all elements on the main page. We found that 65% of them (160 requests) were addressed to the original Jan39.com, 6% (15 requests) were made to Cdnjs.cloudflare.com and 5% (13 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Jan39.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 730.0 kB (23%)

Content Size

3.1 MB

After Optimization

2.4 MB

In fact, the total size of Jan39.com main page is 3.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% 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. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 189.9 kB

  • Original 224.5 kB
  • After minification 193.3 kB
  • After compression 34.6 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 31.2 kB, which is 14% 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 189.9 kB or 85% of the original size.

Image Optimization

-7%

Potential reduce by 124.4 kB

  • Original 1.8 MB
  • After minification 1.7 MB

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. Jan 39 images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 351.9 kB

  • Original 993.8 kB
  • After minification 993.6 kB
  • After compression 641.9 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 351.9 kB or 35% of the original size.

CSS Optimization

-72%

Potential reduce by 63.7 kB

  • Original 88.5 kB
  • After minification 85.8 kB
  • After compression 24.8 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. Jan39.com needs all CSS files to be minified and compressed as it can save up to 63.7 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (26%)

Requests Now

238

After Optimization

175

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

Accessibility Review

jan39.com accessibility score

81

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.

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 IDs are not unique

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

jan39.com 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jan39.com SEO score

73

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    UTF-8

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

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