Tools & Wizards About Us
ponos.co.jp screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ponos.co.jp

ポノス株式会社

Page Load Speed

9.9 sec in total

First Response

3 sec

Resources Loaded

6.8 sec

Page Rendered

157 ms

ponos.co.jp screenshot

About Website

Click here to check amazing Ponos content for United States. Otherwise, check out these important facts you probably never knew about ponos.co.jp

ポノス株式会社の公式企業サイトです。「ナナメウエ、イケテル？」ポノス株式会社は京都に本社を置き、スマートフォン向けゲームアプリを自社で企画・開発する会社です。オリジナルゲームをApp Store、Google Play等のマーケットを通じて日本だけに留まらず、海外市場に向けても配信しています。

Visit ponos.co.jp

Key Findings

We analyzed Ponos.co.jp page load time and found that the first response time was 3 sec and then it took 6.9 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

ponos.co.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value16.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value23.5 s

1/100

10%

Network Requests Diagram

3003 ms

jsapi

22 ms

jquery.cycle.js

829 ms

script.js

334 ms

promoarea.js

354 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original Ponos.co.jp, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Ponos.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.9 kB (3%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 8.0 kB

  • Original 10.4 kB
  • After minification 7.4 kB
  • After compression 2.4 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 3.0 kB, which is 29% 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 8.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 5.6 kB

  • Original 1.2 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. Ponos images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 22.4 kB

  • Original 50.6 kB
  • After minification 49.6 kB
  • After compression 28.2 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 22.4 kB or 44% of the original size.

CSS Optimization

-78%

Potential reduce by 8.0 kB

  • Original 10.3 kB
  • After minification 7.4 kB
  • After compression 2.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. Ponos.co.jp needs all CSS files to be minified and compressed as it can save up to 8.0 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (13%)

Requests Now

40

After Optimization

35

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

3003 ms

jsapi

jsapi

22 ms

jquery.cycle.js

jquery.cycle.js

829 ms

script.js

script.js

334 ms

promoarea.js

promoarea.js

354 ms

default.css

default.css

573 ms

index.css

index.css

583 ms

jquery.min.js

jquery.min.js

33 ms

analytics.js

analytics.js

39 ms

header_bg.gif

header_bg.gif

193 ms

logo.png

logo.png

352 ms

btn_english.png

btn_english.png

169 ms

sitemap.png

sitemap.png

190 ms

gnav_home_on.gif

gnav_home_on.gif

335 ms

gnav_news.gif

gnav_news.gif

195 ms

gnav_service.gif

gnav_service.gif

334 ms

gnav_corporate.gif

gnav_corporate.gif

380 ms

gnav_recruit.gif

gnav_recruit.gif

381 ms

gnav_contact.gif

gnav_contact.gif

387 ms

facebook_icon.png

facebook_icon.png

500 ms

twitter_icon.png

twitter_icon.png

500 ms

mainimg_girlsmons.png

mainimg_girlsmons.png

2688 ms

ttl_news.gif

ttl_news.gif

572 ms

more_orange.png

more_orange.png

573 ms

icon_arrow01.gif

icon_arrow01.gif

587 ms

icon_torics.gif

icon_torics.gif

665 ms

sidebnr_girlsmons02.png

sidebnr_girlsmons02.png

1334 ms

sidebnr_battlecats03.jpg

sidebnr_battlecats03.jpg

1331 ms

sidebnr_battlecats_goods.jpg

sidebnr_battlecats_goods.jpg

949 ms

sidebnr_access.jpg

sidebnr_access.jpg

974 ms

pagetop.gif

pagetop.gif

830 ms

footer_policy.gif

footer_policy.gif

1002 ms

footer_copyright.gif

footer_copyright.gif

1142 ms

footer_link.gif

footer_link.gif

1172 ms

copyright.gif

copyright.gif

1171 ms

gnav_news_on.gif

gnav_news_on.gif

1331 ms

gnav_service_on.gif

gnav_service_on.gif

1342 ms

gnav_corporate_on.gif

gnav_corporate_on.gif

1367 ms

gnav_recruit_on.gif

gnav_recruit_on.gif

1522 ms

gnav_contact_on.gif

gnav_contact_on.gif

1522 ms

collect

collect

12 ms

Accessibility Review

ponos.co.jp accessibility score

73

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.

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

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

Links do not have a discernible name

Best Practices

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

SEO Factors

ponos.co.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ponos.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ponos.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

ponos.co.jp

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