Tools & Wizards About Us
octrise.co.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

octrise.co.jp

東北|秋田|スマホ・タブレットアプリ開発(iOS,Android,Windows)|Webシステム開発|業務システム開発|ソフト開発|株式会社オクトライズ

Page Load Speed

6.7 sec in total

First Response

394 ms

Resources Loaded

6.1 sec

Page Rendered

157 ms

octrise.co.jp screenshot

About Website

Welcome to octrise.co.jp homepage info - get ready to check Octrise best content right away, or after learning these important things about octrise.co.jp

オクトライズは秋田県秋田市にあるアプリ開発,業務システム開発等のソフトウェア開発/設計専門会社です。スマホ・タブレットアプリ(iOS/iPhone/iPad,Android)、Webシステム、業務システム開発を得意としております。お問い合わせ/見積もりは無料で承ります。

Visit octrise.co.jp

Key Findings

We analyzed Octrise.co.jp page load time and found that the first response time was 394 ms and then it took 6.3 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

octrise.co.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value4.9 s

78/100

10%

Network Requests Diagram

octrise.co.jp

394 ms

octrise.co.jp

1384 ms

bootstrap.min.css

1295 ms

jquery.sidr.dark.css

904 ms

style.css

940 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 85% of them (41 requests) were addressed to the original Octrise.co.jp, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Octrise.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (54%)

Content Size

2.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Octrise.co.jp main page is 2.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. 25% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 33.7 kB

  • Original 44.5 kB
  • After minification 44.5 kB
  • After compression 10.8 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 33.7 kB or 76% of the original size.

Image Optimization

-56%

Potential reduce by 1.5 MB

  • Original 2.6 MB
  • After minification 1.1 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. Obviously, Octrise needs image optimization as it can save up to 1.5 MB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 2.0 kB

  • Original 93.5 kB
  • After minification 93.5 kB
  • After compression 91.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 1.2 kB

  • Original 38.6 kB
  • After minification 38.6 kB
  • After compression 37.4 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. Octrise.co.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (59%)

Requests Now

46

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

octrise.co.jp

octrise.co.jp

394 ms

octrise.co.jp

octrise.co.jp

1384 ms

bootstrap.min.css

bootstrap.min.css

1295 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

904 ms

style.css

style.css

940 ms

style.min.css

style.min.css

1415 ms

styles.css

styles.css

766 ms

lightbox.min.css

lightbox.min.css

802 ms

overrides.css

overrides.css

949 ms

jquery.min.js

jquery.min.js

1484 ms

jquery-migrate.min.js

jquery-migrate.min.js

978 ms

js

js

74 ms

jquery-1.10.1.min.js

jquery-1.10.1.min.js

25 ms

jquery.easing.min.js

jquery.easing.min.js

999 ms

rotate.js

rotate.js

1188 ms

page_top.js

page_top.js

1195 ms

bootstrap.min.js

bootstrap.min.js

44 ms

hooks.min.js

hooks.min.js

1327 ms

i18n.min.js

i18n.min.js

1351 ms

index.js

index.js

1389 ms

index.js

index.js

1393 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

1444 ms

purify.min.js

purify.min.js

1616 ms

panzoom.min.js

panzoom.min.js

1616 ms

jquery.lightbox.js

jquery.lightbox.js

1618 ms

jquery.easy-ticker.min.js

jquery.easy-ticker.min.js

1615 ms

news_list.js

news_list.js

1653 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

86 ms

analytics.js

analytics.js

120 ms

business_appli.png

business_appli.png

214 ms

greeting_img.gif

greeting_img.gif

206 ms

ennea_main.jpg

ennea_main.jpg

669 ms

banner3.png

banner3.png

2846 ms

octrise_hp.png

octrise_hp.png

1872 ms

kira2d_main.jpg

kira2d_main.jpg

494 ms

ae46b1f460ee46f789c27b264a6cb421.png

ae46b1f460ee46f789c27b264a6cb421.png

856 ms

logo.jpg

logo.jpg

597 ms

16190236_100_JP.gif

16190236_100_JP.gif

704 ms

logo_rotate_1.gif

logo_rotate_1.gif

806 ms

logo_rotate_2.gif

logo_rotate_2.gif

869 ms

navi_list.gif

navi_list.gif

910 ms

footer_logo.jpg

footer_logo.jpg

1013 ms

go_top.png

go_top.png

1062 ms

business_web.png

business_web.png

845 ms

business_old.png

business_old.png

850 ms

collect

collect

13 ms

js

js

42 ms

main.js

main.js

11 ms

Accessibility Review

octrise.co.jp accessibility score

90

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

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

Best Practices

octrise.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

octrise.co.jp SEO score

93

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

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 Octrise.co.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 Octrise.co.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

octrise.co.jp

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