12.1 sec in total
574 ms
11.2 sec
337 ms
Welcome to colopl.jp homepage info - get ready to check Colopl best content for China right away, or after learning these important things about colopl.jp
株式会社コロプラは、携帯位置情報ゲーム「コロニーな生活」の運用をしている会社です。
Visit colopl.jpWe analyzed Colopl.jp page load time and found that the first response time was 574 ms and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
colopl.jp performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value3.2 s
71/100
25%
Value3.0 s
94/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.0 s
96/100
10%
574 ms
365 ms
368 ms
373 ms
15 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Colopl.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Pc.colopl.jp.
Page size can be reduced by 99.0 kB (7%)
1.5 MB
1.4 MB
In fact, the total size of Colopl.jp main page is 1.5 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. 25% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 16.7 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 16.7 kB or 72% of the original size.
Potential reduce by 51.4 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. Colopl images are well optimized though.
Potential reduce by 25.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 25.8 kB or 40% of the original size.
Potential reduce by 5.1 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. Colopl.jp needs all CSS files to be minified and compressed as it can save up to 5.1 kB or 71% of the original size.
Number of requests can be reduced by 7 (9%)
79
72
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Colopl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
welcome.html
574 ms
html5reset.css
365 ms
layout.css
368 ms
ui.tabs.css
373 ms
jsapi
15 ms
common.js
376 ms
jquery-1.2.3.pack.js
984 ms
ui.tabs.pack.js
720 ms
ui.tabs.ext.pack.js
727 ms
swfobject.js
1091 ms
jquery.min.js
30 ms
ga.js
27 ms
__utm.gif
11 ms
bg.jpg
1304 ms
logo_plus.gif
361 ms
logo.png
726 ms
catch.png
908 ms
bg_signboard.png
1460 ms
1.jpg
1124 ms
bg_clearboard.png
921 ms
ttl_colopl.png
1441 ms
read_colopl.png
1444 ms
img_pla.png
1651 ms
ttl_pla.png
1499 ms
read_pla.png
1845 ms
img_chara.png
2350 ms
ttl_iroiro.png
1836 ms
read_iroiro.png
1848 ms
img_coloca.png
2223 ms
bg_join.jpg
2636 ms
ttl_join.png
2585 ms
join.gif
2219 ms
ttl_type.gif
2221 ms
read_join.png
2774 ms
btn_join.jpg
3192 ms
ttl_enjoy.png
3010 ms
ttl_enjoy11.jpg
2893 ms
img_enjoy11.jpg
3142 ms
ttl_enjoy12.jpg
3196 ms
img_enjoy12.jpg
3317 ms
ttl_enjoy13.jpg
3439 ms
img_enjoy13.jpg
3600 ms
ttl_enjoy21.jpg
3929 ms
img_enjoy21.jpg
3911 ms
ttl_enjoy22.jpg
3979 ms
img_enjoy22.jpg
3871 ms
ttl_enjoy23.jpg
4168 ms
img_enjoy23.jpg
4166 ms
ttl_enjoy31.jpg
4400 ms
img_enjoy31.jpg
4110 ms
ttl_enjoy32.jpg
3753 ms
img_enjoy32.jpg
3869 ms
ttl_enjoy33.jpg
3813 ms
img_enjoy33.jpg
3806 ms
ttl_enjoy41.jpg
3877 ms
img_enjoy41.jpg
3572 ms
ttl_enjoy42.jpg
3577 ms
img_enjoy42.jpg
4000 ms
ttl_enjoy43.jpg
3859 ms
img_enjoy43.jpg
3837 ms
ttl_other.jpg
3911 ms
bg_other.gif
3564 ms
ttl_other01.png
3877 ms
ttl_other02.jpg
3698 ms
btn_other01.jpg
3930 ms
btn_other02.jpg
3960 ms
img_other.jpg
3862 ms
join.gif
3511 ms
nav01.jpg
4035 ms
nav02.jpg
4050 ms
nav03.jpg
4148 ms
nav04.jpg
4036 ms
2.jpg
4163 ms
3.jpg
4093 ms
4.jpg
4560 ms
5.jpg
3889 ms
6.jpg
3107 ms
7.jpg
2133 ms
8.jpg
1398 ms
9.jpg
931 ms
colopl.jp accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
colopl.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
colopl.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Colopl.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 Colopl.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.
colopl.jp
Open Graph description is not detected on the main page of Colopl. 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: