Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

enterprisezine.jp

EnterpriseZine（エンタープライズジン）

Page Load Speed

5.5 sec in total

First Response

408 ms

Resources Loaded

3.7 sec

Page Rendered

1.4 sec

About Website

Click here to check amazing Enterprise Zine content for Japan. Otherwise, check out these important facts you probably never knew about enterprisezine.jp

「EnterpriseZine」（エンタープライズジン）は、翔泳社が運営する企業のIT活用とビジネス成長を支援するITリーダー向け専門メディアです。データテクノロジー/情報セキュリティ/システム運用の最新動向を中心に、企業ITに関する多様な情報をお届けしています。

Visit enterprisezine.jp

Key Findings

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

Performance Metrics

enterprisezine.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.154

74/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

enterprisezine.jp

408 ms

enterprisezine.jp

1279 ms

gtm.js

52 ms

bootstrap.custom.css

167 ms

main-enterprisezine.css

180 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Enterprisezine.jp, 43% (36 requests) were made to Ez-cdn.shoeisha.jp and 11% (9 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

937.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 162.1 kB

  • Original 191.9 kB
  • After minification 162.0 kB
  • After compression 29.7 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 29.8 kB, which is 16% 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 162.1 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 6.5 kB

  • Original 329.4 kB
  • After minification 323.0 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. Enterprise Zine images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 110.6 kB

  • Original 662.2 kB
  • After minification 662.2 kB
  • After compression 551.6 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 110.6 kB or 17% of the original size.

CSS Optimization

-13%

Potential reduce by 5.1 kB

  • Original 38.3 kB
  • After minification 38.3 kB
  • After compression 33.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. Enterprisezine.jp needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (53%)

Requests Now

81

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enterprise Zine. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

enterprisezine.jp accessibility score

63

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

Best Practices

enterprisezine.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

enterprisezine.jp SEO score

92

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

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

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

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