Tools & Wizards About Us
fis-s.co.jp screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fis-s.co.jp

次世代経営コンサルティングの株式会社FISソリューションズ

Page Load Speed

6.8 sec in total

First Response

627 ms

Resources Loaded

5.8 sec

Page Rendered

325 ms

fis-s.co.jp screenshot

About Website

Welcome to fis-s.co.jp homepage info - get ready to check Fis S best content right away, or after learning these important things about fis-s.co.jp

FISソリューションズは、電話工事、LAN工事からビジネスフォン、コピー機の導入など。 情報通信コンサルタントのプロがお客様のオフィス環境について幅広くサポートいたします。

Visit fis-s.co.jp

Key Findings

We analyzed Fis-s.co.jp page load time and found that the first response time was 627 ms and then it took 6.1 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

fis-s.co.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

fis-s.co.jp

627 ms

fis-s.co.jp

1050 ms

cssreset-min.css

30 ms

style.css

213 ms

jquery-1.11.2.min.js

625 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 86% of them (61 requests) were addressed to the original Fis-s.co.jp, 7% (5 requests) were made to Ipa.go.jp and 3% (2 requests) were made to Accessilens.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Fis-s.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.5 kB (28%)

Content Size

628.3 kB

After Optimization

452.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fis-s.co.jp main page is 628.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 401.6 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 161.8 kB

  • Original 172.4 kB
  • After minification 116.7 kB
  • After compression 10.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 55.7 kB, which is 32% 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 161.8 kB or 94% of the original size.

Image Optimization

-2%

Potential reduce by 7.6 kB

  • Original 401.6 kB
  • After minification 394.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. Fis S images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 4.0 kB

  • Original 46.0 kB
  • After minification 45.3 kB
  • After compression 42.0 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

-25%

Potential reduce by 2.1 kB

  • Original 8.4 kB
  • After minification 8.3 kB
  • After compression 6.3 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. Fis-s.co.jp needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (15%)

Requests Now

68

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fis-s.co.jp

fis-s.co.jp

627 ms

fis-s.co.jp

fis-s.co.jp

1050 ms

cssreset-min.css

cssreset-min.css

30 ms

style.css

style.css

213 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

625 ms

rollover.js

rollover.js

892 ms

opacity-rollover2.1.js

opacity-rollover2.1.js

891 ms

smoothScrollEx.js

smoothScrollEx.js

582 ms

mywideslider.js

mywideslider.js

583 ms

icatw2.js

icatw2.js

536 ms

unitoolbar.js

unitoolbar.js

484 ms

hlogo.gif

hlogo.gif

197 ms

hicon02.gif

hicon02.gif

198 ms

hicon03.gif

hicon03.gif

177 ms

gnav01_n.gif

gnav01_n.gif

198 ms

gnav02_n.gif

gnav02_n.gif

199 ms

gnav03_n.gif

gnav03_n.gif

177 ms

gnav04_n.gif

gnav04_n.gif

353 ms

gnav05_n.gif

gnav05_n.gif

354 ms

gnav06_n.gif

gnav06_n.gif

391 ms

gnav07_n.gif

gnav07_n.gif

394 ms

sound_off.png

sound_off.png

392 ms

tnews_ttl.gif

tnews_ttl.gif

394 ms

tnews_tag01.gif

tnews_tag01.gif

528 ms

bnr_new-grad.gif

bnr_new-grad.gif

528 ms

ticon_ttl.gif

ticon_ttl.gif

588 ms

ticon_btn.gif

ticon_btn.gif

588 ms

tsv_ttl.png

tsv_ttl.png

597 ms

tsv_img01.gif

tsv_img01.gif

588 ms

tsv_img03.gif

tsv_img03.gif

703 ms

tsv_img04.gif

tsv_img04.gif

703 ms

tsv_img05.gif

tsv_img05.gif

783 ms

tbnr_img_club.gif

tbnr_img_club.gif

1326 ms

tbnr_ttl_club.gif

tbnr_ttl_club.gif

787 ms

tbnr_img_csr.gif

tbnr_img_csr.gif

1524 ms

tbnr_ttl_csr.gif

tbnr_ttl_csr.gif

881 ms

fBnr01.jpg

fBnr01.jpg

1522 ms

tbnr_ttl_sustainable.png

tbnr_ttl_sustainable.png

977 ms

tbnr_img_sdgs.png

tbnr_img_sdgs.png

1324 ms

tbnr_ttl_sdgs.png

tbnr_ttl_sdgs.png

1055 ms

tbnr01.gif

tbnr01.gif

1330 ms

tbnr02.gif

tbnr02.gif

1324 ms

tbnr03.gif

tbnr03.gif

1520 ms

macloud.jpg

macloud.jpg

1501 ms

FIS-logo-min.jpeg

FIS-logo-min.jpeg

1518 ms

totop.gif

totop.gif

1519 ms

banner01.png

banner01.png

1654 ms

jquery.xdomainrequest.min.js

jquery.xdomainrequest.min.js

150 ms

icatw2_sub.js

icatw2_sub.js

156 ms

ftlogo.gif

ftlogo.gif

1544 ms

ftpmark.gif

ftpmark.gif

1546 ms

03_tr_20th_gp_lg.png

03_tr_20th_gp_lg.png

1527 ms

dxmark.jpg

dxmark.jpg

1524 ms

gxleague.jpg

gxleague.jpg

2668 ms

mov_shade.png

mov_shade.png

1660 ms

reset_icatw2.css

reset_icatw2.css

149 ms

IPARssReader.php

IPARssReader.php

1368 ms

tnews_lm.gif

tnews_lm.gif

1563 ms

sokus.js

sokus.js

965 ms

ticon_bg.jpg

ticon_bg.jpg

2129 ms

tsv_bg.gif

tsv_bg.gif

1528 ms

ft_lm.gif

ft_lm.gif

1526 ms

unitoolbar.class.js

unitoolbar.class.js

661 ms

icatw2_img.png

icatw2_img.png

151 ms

gnav01_r.gif

gnav01_r.gif

204 ms

gnav02_r.gif

gnav02_r.gif

196 ms

gnav03_r.gif

gnav03_r.gif

176 ms

gnav04_r.gif

gnav04_r.gif

201 ms

gnav05_r.gif

gnav05_r.gif

199 ms

gnav06_r.gif

gnav06_r.gif

196 ms

gnav07_r.gif

gnav07_r.gif

354 ms

Accessibility Review

fis-s.co.jp accessibility score

68

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

fis-s.co.jp 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fis-s.co.jp SEO score

89

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

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 Fis-s.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 Fis-s.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

fis-s.co.jp

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