Tools & Wizards About Us
otech.ne.jp screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

otech.ne.jp

OTECH

Page Load Speed

12.4 sec in total

First Response

257 ms

Resources Loaded

11.9 sec

Page Rendered

237 ms

otech.ne.jp screenshot

About Website

Welcome to otech.ne.jp homepage info - get ready to check OTECH best content right away, or after learning these important things about otech.ne.jp

オーシャンテクノロジーはテレコムソリューションサービスおよびネットワークサービスを提供しております。コンシューマー向けの革新的なテレコムソリューションを、ワールドワイドで提供し業界で高い評価を得ております。テレコム業界のリーディングカンパニーとして今後も様々な製品を提供し続けてまいります。

Visit otech.ne.jp

Key Findings

We analyzed Otech.ne.jp page load time and found that the first response time was 257 ms and then it took 12.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Otech.ne.jp rating and web reputation

Performance Metrics

otech.ne.jp performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.4 s

100/100

10%

Network Requests Diagram

jp

257 ms

6130 ms

css

25 ms

styles.css

476 ms

style.css

975 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 91% of them (69 requests) were addressed to the original Otech.ne.jp, 7% (5 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Otech.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 856.6 kB (37%)

Content Size

2.3 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Otech.ne.jp main page is 2.3 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 52.4 kB

  • Original 61.1 kB
  • After minification 54.8 kB
  • After compression 8.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 52.4 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 71.8 kB

  • Original 1.3 MB
  • After minification 1.2 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. OTECH images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 564.2 kB

  • Original 737.7 kB
  • After minification 574.6 kB
  • After compression 173.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 564.2 kB or 76% of the original size.

CSS Optimization

-87%

Potential reduce by 168.3 kB

  • Original 193.2 kB
  • After minification 137.3 kB
  • After compression 25.0 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. Otech.ne.jp needs all CSS files to be minified and compressed as it can save up to 168.3 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

65

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jp

jp

257 ms

6130 ms

css

css

25 ms

styles.css

styles.css

476 ms

style.css

style.css

975 ms

responsive.css

responsive.css

490 ms

jquery.js

jquery.js

1270 ms

jquery-migrate.min.js

jquery-migrate.min.js

498 ms

responsive-modernizr.min.js

responsive-modernizr.min.js

936 ms

jquery.js

jquery.js

2236 ms

style.css

style.css

684 ms

fontello.css

fontello.css

881 ms

preview.js

preview.js

908 ms

jquery.tp.min.js

jquery.tp.min.js

1445 ms

jquery.tr.min.js

jquery.tr.min.js

1755 ms

setting.css

setting.css

1148 ms

css

css

32 ms

settings.css

settings.css

1352 ms

jquery.tm.js

jquery.tm.js

1648 ms

jquery.fancybox.css

jquery.fancybox.css

1381 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1588 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

1618 ms

jquery.form.min.js

jquery.form.min.js

512 ms

scripts.js

scripts.js

251 ms

responsive-scripts.min.js

responsive-scripts.min.js

242 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

484 ms

copy-logo.png

copy-logo.png

260 ms

dataservices-bg.png

dataservices-bg.png

1863 ms

data-services-text-jp.png

data-services-text-jp.png

256 ms

data-services-subtext-jp.png

data-services-subtext-jp.png

471 ms

web-service-bg.jpg

web-service-bg.jpg

1240 ms

web-service-shape.png

web-service-shape.png

238 ms

logo-codeigniter.png

logo-codeigniter.png

235 ms

logo-php.png

logo-php.png

471 ms

logo-mysql.png

logo-mysql.png

469 ms

logo-wordpress.png

logo-wordpress.png

511 ms

logo-csshtml.png

logo-csshtml.png

696 ms

logo-eccube.png

logo-eccube.png

701 ms

web-service-text-bg.png

web-service-text-bg.png

702 ms

iptv-bg.jpg

iptv-bg.jpg

1530 ms

iptv-channels.png

iptv-channels.png

1154 ms

iphone.png

iphone.png

1170 ms

ipad.png

ipad.png

1401 ms

set-top-box.png

set-top-box.png

1384 ms

remote-control.png

remote-control.png

1404 ms

cloud-bg.png

cloud-bg.png

1481 ms

cloud.png

cloud.png

1613 ms

servers.png

servers.png

1634 ms

application.png

application.png

1638 ms

data.png

data.png

1724 ms

software-platform.png

software-platform.png

1783 ms

virtual-desktop.png

virtual-desktop.png

1843 ms

network-solutions-icon.png

network-solutions-icon.png

1870 ms

cloud-services-icon.png

cloud-services-icon.png

1872 ms

managed-data-networks-icon.png

managed-data-networks-icon.png

2035 ms

iptv.jpg

iptv.jpg

2040 ms

web-and-software-icon.png

web-and-software-icon.png

2077 ms

web-hosting-domain-registration-icon.png

web-hosting-domain-registration-icon.png

2123 ms

search-engine-optimization-icon.png

search-engine-optimization-icon.png

2104 ms

cdn-services-icon.png

cdn-services-icon.png

2110 ms

carrier-services-icon.png

carrier-services-icon.png

2219 ms

japan-toll-free-number-icon.png

japan-toll-free-number-icon.png

2295 ms

agent-login-ja.png

agent-login-ja.png

259 ms

international-calling-cards-icon.png

international-calling-cards-icon.png

2291 ms

services-box-bg.png

services-box-bg.png

244 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

7 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

8 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

14 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

13 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

13 ms

revicons.woff

revicons.woff

2109 ms

loader.gif

loader.gif

2127 ms

service-bullet.png

service-bullet.png

2134 ms

bullet20px.png

bullet20px.png

2005 ms

revicons.ttf

revicons.ttf

257 ms

revicons.svg

revicons.svg

267 ms

Accessibility Review

otech.ne.jp accessibility score

86

Accessibility Issues

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

otech.ne.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

SEO Factors

otech.ne.jp SEO score

58

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otech.ne.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Otech.ne.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

otech.ne.jp

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