Tools & Wizards About Us
swagapp.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

swagapp.co.jp

株式会社イグニス　IGNIS LTD. |

Page Load Speed

5.4 sec in total

First Response

543 ms

Resources Loaded

4.3 sec

Page Rendered

518 ms

swagapp.co.jp screenshot

About Website

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

スマートフォンアプリとスマートフォン向けゲームの企画、開発、運営を行うイグニスの公式ホームページです。イグニスのコーポレート情報、プロダクツ情報、採用情報、IR情報をご覧いただけます。

Visit swagapp.co.jp

Key Findings

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

Performance Metrics

swagapp.co.jp performance score

0

Network Requests Diagram

swagapp.co.jp

543 ms

1923.co.jp

1228 ms

styles.css

306 ms

styles.css

306 ms

slimbox2.css

319 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Swagapp.co.jp, 63% (44 requests) were made to 1923.co.jp and 11% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source 1923.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

3.4 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 42.9 kB

  • Original 56.2 kB
  • After minification 54.1 kB
  • After compression 13.3 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 42.9 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 189.2 kB

  • Original 2.8 MB
  • After minification 2.6 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. Swagapp images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 195.4 kB

  • Original 293.8 kB
  • After minification 257.5 kB
  • After compression 98.4 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 195.4 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 178.3 kB

  • Original 213.6 kB
  • After minification 185.4 kB
  • After compression 35.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. Swagapp.co.jp needs all CSS files to be minified and compressed as it can save up to 178.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (51%)

Requests Now

68

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swagapp.co.jp

swagapp.co.jp

543 ms

1923.co.jp

1923.co.jp

1228 ms

styles.css

styles.css

306 ms

styles.css

styles.css

306 ms

slimbox2.css

slimbox2.css

319 ms

lightbox.min.css

lightbox.min.css

353 ms

jquery.js

jquery.js

950 ms

jquery-migrate.min.js

jquery-migrate.min.js

451 ms

slimbox2.js

slimbox2.js

456 ms

slimbox2_autoload.js

slimbox2_autoload.js

456 ms

wp-page-numbers.css

wp-page-numbers.css

475 ms

reset.css

reset.css

528 ms

bootstrap.min.css

bootstrap.min.css

1055 ms

font-awesome.css

font-awesome.css

16 ms

default.css

default.css

758 ms

style.css

style.css

909 ms

jquery.min.js

jquery.min.js

5 ms

bootstrap.min.js

bootstrap.min.js

790 ms

flexslider.css

flexslider.css

558 ms

public.css

public.css

734 ms

jquery.form.min.js

jquery.form.min.js

764 ms

scripts.js

scripts.js

831 ms

scripts.js

scripts.js

968 ms

jquery.touchwipe.min.js

jquery.touchwipe.min.js

968 ms

jquery.lightbox.min.js

jquery.lightbox.min.js

969 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1030 ms

bookmark_button.js

bookmark_button.js

343 ms

plusone.js

plusone.js

31 ms

analytics.js

analytics.js

10 ms

collect

collect

13 ms

button-only@2x.png

button-only@2x.png

172 ms

logo.png

logo.png

153 ms

slide01-1498x477-1498x476.jpg

slide01-1498x477-1498x476.jpg

709 ms

slide02-1498x477-1498x476.jpg

slide02-1498x477-1498x476.jpg

814 ms

destroyer_icon_1024.png

destroyer_icon_1024.png

1705 ms

2d6c2a8d2c7f3620cc8d0b847bf5a3ab.png

2d6c2a8d2c7f3620cc8d0b847bf5a3ab.png

652 ms

67f6e43d8e8709aa6ced675aa4c4b7ba.png

67f6e43d8e8709aa6ced675aa4c4b7ba.png

339 ms

banner10000.png

banner10000.png

627 ms

icon.png

icon.png

1250 ms

56e932729ec6c019df977759d6c9281e.jpg

56e932729ec6c019df977759d6c9281e.jpg

814 ms

87a4b38a53f3bde5c46c61ab86b5e2fe.png

87a4b38a53f3bde5c46c61ab86b5e2fe.png

798 ms

icon-512.png

icon-512.png

1236 ms

icon_breaker-new.png

icon_breaker-new.png

1710 ms

recruit_ceocto.png

recruit_ceocto.png

1128 ms

btn_career.png

btn_career.png

1193 ms

698659aea711eddfc1683bcda1222724.png

698659aea711eddfc1683bcda1222724.png

1445 ms

footTopic02.jpg

footTopic02.jpg

1382 ms

footTopic03.jpg

footTopic03.jpg

1412 ms

footTopic04.jpg

footTopic04.jpg

1405 ms

ignis_logo_rw.jpg

ignis_logo_rw.jpg

1571 ms

icon_target.gif

icon_target.gif

1538 ms

237 ms

sdk.js

sdk.js

177 ms

widgets.js

widgets.js

102 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

87 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

67 ms

fastbutton

fastbutton

153 ms

bg_direction_nav.png

bg_direction_nav.png

1258 ms

postmessageRelay

postmessageRelay

104 ms

button.65b4bc8f0d6592fdc51d322b3f197660.js

button.65b4bc8f0d6592fdc51d322b3f197660.js

139 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

57 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

52 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

40 ms

rpc:shindig_random.js

rpc:shindig_random.js

43 ms

147 ms

xd_arbiter.php

xd_arbiter.php

74 ms

xd_arbiter.php

xd_arbiter.php

132 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

tweet_button.64a917b4a230f163048902c783e1530f.ja.html

44 ms

jot

jot

83 ms

SEO Factors

swagapp.co.jp SEO score

0

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

swagapp.co.jp

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