Tools & Wizards About Us
griphone.co.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

griphone.co.jp

株式会社グリフォン | 東京、渋谷発。唯一無二のオンラインゲームカンパニーを目指して。

Page Load Speed

7.6 sec in total

First Response

323 ms

Resources Loaded

6.7 sec

Page Rendered

627 ms

griphone.co.jp screenshot

About Website

Visit griphone.co.jp now to see the best up-to-date Griphone content for Japan and also check out these interesting facts you probably never knew about griphone.co.jp

株式会社グリフォンはオンラインゲームの開発、運用を行うベンチャー企業です。

Visit griphone.co.jp

Key Findings

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

Performance Metrics

griphone.co.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value12.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value21.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value22.9 s

1/100

10%

Network Requests Diagram

griphone.co.jp

323 ms

common.css

438 ms

jquery-1.9.1.min.js

731 ms

selectivizr-min.js

294 ms

jquery.flexslider-min.js

440 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 64% of them (75 requests) were addressed to the original Griphone.co.jp, 22% (26 requests) were made to Maps.googleapis.com and 8% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Griphone.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 559.4 kB (18%)

Content Size

3.1 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Griphone.co.jp main page is 3.1 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 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.3 kB

  • Original 59.3 kB
  • After minification 57.1 kB
  • After compression 10.0 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 49.3 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 107.8 kB

  • Original 2.4 MB
  • After minification 2.3 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. Griphone images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 386.7 kB

  • Original 603.5 kB
  • After minification 601.9 kB
  • After compression 216.8 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 386.7 kB or 64% of the original size.

CSS Optimization

-76%

Potential reduce by 15.5 kB

  • Original 20.4 kB
  • After minification 20.3 kB
  • After compression 4.8 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. Griphone.co.jp needs all CSS files to be minified and compressed as it can save up to 15.5 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (19%)

Requests Now

112

After Optimization

91

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

griphone.co.jp

griphone.co.jp

323 ms

common.css

common.css

438 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

731 ms

selectivizr-min.js

selectivizr-min.js

294 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

440 ms

mainfunction.js

mainfunction.js

299 ms

js

js

80 ms

map.js

map.js

300 ms

analytics.js

analytics.js

73 ms

logo.gif

logo.gif

293 ms

h2.gif

h2.gif

295 ms

nav_service.gif

nav_service.gif

296 ms

nav_ceomessage.gif

nav_ceomessage.gif

296 ms

nav_company.gif

nav_company.gif

298 ms

nav_recruit.gif

nav_recruit.gif

300 ms

nav_contact.gif

nav_contact.gif

582 ms

hero01.gif

hero01.gif

584 ms

hero04.jpg

hero04.jpg

1166 ms

hero05.jpg

hero05.jpg

1206 ms

hero06.jpg

hero06.jpg

1377 ms

ttl_news.gif

ttl_news.gif

588 ms

ttl_service.gif

ttl_service.gif

873 ms

icon_title.gif

icon_title.gif

874 ms

img_diva.jpg

img_diva.jpg

1606 ms

img_mae.jpg

img_mae.jpg

1796 ms

img_king.jpg

img_king.jpg

1776 ms

ttl_ceo_message.gif

ttl_ceo_message.gif

1455 ms

img_vision.gif

img_vision.gif

1832 ms

img_vision320.gif

img_vision320.gif

1821 ms

btn_vision.gif

btn_vision.gif

1747 ms

ttl_company.gif

ttl_company.gif

1900 ms

btn_map.gif

btn_map.gif

2038 ms

ttl_recruit.gif

ttl_recruit.gif

2066 ms

top_btn_interview01.jpg

top_btn_interview01.jpg

2393 ms

top_btn_interview02.jpg

top_btn_interview02.jpg

2405 ms

top_btn_interview03.jpg

top_btn_interview03.jpg

2435 ms

top_interview_bg.png

top_interview_bg.png

2192 ms

ttl_contact.gif

ttl_contact.gif

2331 ms

btn_contact.gif

btn_contact.gif

2363 ms

logo.png

logo.png

2484 ms

index.html

index.html

2586 ms

bg_direction_nav.png

bg_direction_nav.png

2612 ms

collect

collect

26 ms

2013031801.jpg

2013031801.jpg

147 ms

20160219.jpg

20160219.jpg

293 ms

20160208.jpg

20160208.jpg

293 ms

20150714.jpg

20150714.jpg

294 ms

20150929.jpg

20150929.jpg

439 ms

20150917.jpg

20150917.jpg

319 ms

20150316.jpg

20150316.jpg

441 ms

20150817.png

20150817.png

731 ms

20150717.png

20150717.png

583 ms

20150615.jpeg

20150615.jpeg

587 ms

20150609.png

20150609.png

615 ms

20150605.png

20150605.png

730 ms

20150430.jpg

20150430.jpg

876 ms

20150428.jpg

20150428.jpg

1021 ms

20150331.jpg

20150331.jpg

882 ms

20150326.jpg

20150326.jpg

908 ms

20150313.jpg

20150313.jpg

1020 ms

20150224.jpg

20150224.jpg

1165 ms

20150223.jpg

20150223.jpg

1168 ms

20150120_1.jpg

20150120_1.jpg

1317 ms

20141222.jpg

20141222.jpg

1346 ms

20140527.jpg

20140527.jpg

1464 ms

20140919.jpg

20140919.jpg

1467 ms

20140917.jpg

20140917.jpg

1601 ms

20140723.jpg

20140723.jpg

1615 ms

20140722.jpg

20140722.jpg

1752 ms

20140613.jpg

20140613.jpg

1782 ms

20140303.jpg

20140303.jpg

1901 ms

20140227.jpg

20140227.jpg

1917 ms

20140214.jpg

20140214.jpg

2045 ms

2013121001.jpg

2013121001.jpg

2054 ms

2013091801.jpg

2013091801.jpg

2193 ms

2013082901.jpg

2013082901.jpg

2218 ms

2013031802.jpg

2013031802.jpg

2337 ms

common.js

common.js

20 ms

map.js

map.js

52 ms

util.js

util.js

41 ms

marker.js

marker.js

52 ms

stats.js

stats.js

52 ms

onion.js

onion.js

20 ms

openhand_8_8.cur

openhand_8_8.cur

84 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

76 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

73 ms

controls.js

controls.js

26 ms

map_logo.png

map_logo.png

311 ms

css

css

72 ms

transparent.png

transparent.png

43 ms

google4.png

google4.png

64 ms

mapcnt6.png

mapcnt6.png

82 ms

sv5.png

sv5.png

91 ms

tmapctrl.png

tmapctrl.png

82 ms

cb_scout5.png

cb_scout5.png

94 ms

tmapctrl4.png

tmapctrl4.png

82 ms

imgs8.png

imgs8.png

82 ms

vt

vt

51 ms

vt

vt

59 ms

vt

vt

56 ms

vt

vt

174 ms

vt

vt

60 ms

vt

vt

55 ms

vt

vt

176 ms

vt

vt

70 ms

vt

vt

175 ms

vt

vt

70 ms

vt

vt

78 ms

vt

vt

81 ms

vt

vt

211 ms

vt

vt

96 ms

vt

vt

211 ms

vt

vt

208 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

65 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

96 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

139 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

142 ms

Accessibility Review

griphone.co.jp accessibility score

83

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

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

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

griphone.co.jp SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

griphone.co.jp

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