Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

otakuma.net

おたくま経済新聞

Page Load Speed

7.5 sec in total

First Response

1 sec

Resources Loaded

5.9 sec

Page Rendered

593 ms

otakuma.net screenshot

About Website

Click here to check amazing Otakuma content for Japan. Otherwise, check out these important facts you probably never knew about otakuma.net

ネットでの話題を中心に、商品レビューや独自コラム、取材記事など幅広く配信中!

Visit otakuma.net

Key Findings

We analyzed Otakuma.net page load time and found that the first response time was 1 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

otakuma.net performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value4,000 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

otakuma.net

1002 ms

style.min.css

822 ms

style.css

827 ms

jquery.js

1063 ms

jquery-migrate.min.js

723 ms

Our browser made a total of 168 requests to load all elements on the main page. We found that 61% of them (102 requests) were addressed to the original Otakuma.net, 9% (15 requests) were made to Pagead2.googlesyndication.com and 7% (12 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Otakuma.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 457.2 kB (12%)

Content Size

3.8 MB

After Optimization

3.3 MB

In fact, the total size of Otakuma.net main page is 3.8 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. 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. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 284.3 kB

  • Original 319.9 kB
  • After minification 316.0 kB
  • After compression 35.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. 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 284.3 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 57.2 kB

  • Original 2.7 MB
  • After minification 2.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. Otakuma images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 106.6 kB

  • Original 670.1 kB
  • After minification 670.1 kB
  • After compression 563.5 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 106.6 kB or 16% of the original size.

CSS Optimization

-26%

Potential reduce by 9.0 kB

  • Original 35.2 kB
  • After minification 35.2 kB
  • After compression 26.2 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. Otakuma.net needs all CSS files to be minified and compressed as it can save up to 9.0 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (32%)

Requests Now

161

After Optimization

109

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

Accessibility Review

otakuma.net accessibility score

73

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

otakuma.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

otakuma.net SEO score

99

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otakuma.net 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 Otakuma.net 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 Otakuma. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: