14.2 sec in total
1.1 sec
13 sec
147 ms
Welcome to colossal.jp homepage info - get ready to check Colossal best content right away, or after learning these important things about colossal.jp
無料のアクセス解析を使って個人サイトや自社サイトの総訪問者数やコンバージョン数などのデータからサイトをより良くするために知っておきたいアクセス解析についてご紹介します。
Visit colossal.jpWe analyzed Colossal.jp page load time and found that the first response time was 1.1 sec and then it took 13.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
colossal.jp performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.9 s
98/100
25%
Value2.0 s
99/100
10%
Value170 ms
92/100
30%
Value0.184
66/100
15%
Value1.5 s
100/100
10%
1122 ms
797 ms
615 ms
844 ms
1129 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 68% of them (26 requests) were addressed to the original Colossal.jp, 11% (4 requests) were made to Ace-analyzer.com and 8% (3 requests) were made to User1.colossal.jp. The less responsive or slowest element that took the longest time to load (4.9 sec) relates to the external source Ace-analyzer.com.
Page size can be reduced by 34.1 kB (35%)
96.3 kB
62.3 kB
In fact, the total size of Colossal.jp main page is 96.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. Only 5% of websites need less resources to load. Images take 61.6 kB which makes up the majority of the site volume.
Potential reduce by 12.8 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 12.8 kB or 77% of the original size.
Potential reduce by 6.6 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. Obviously, Colossal needs image optimization as it can save up to 6.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.3 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 11.3 kB or 84% of the original size.
Potential reduce by 3.4 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. Colossal.jp needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 74% of the original size.
Number of requests can be reduced by 10 (27%)
37
27
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Colossal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
colossal.jp
1122 ms
base.css
797 ms
nav.css
615 ms
AC_RunActiveContent.js
844 ms
flash.js
1129 ms
getstats_web.js.php
2041 ms
getstats.js.php
350 ms
pmember_getstats.js.php
587 ms
getstats.js.php
441 ms
getstats.js.php
523 ms
mainbg.gif
180 ms
bg_header.jpg
208 ms
logo.gif
395 ms
spcaer.gif
269 ms
bg_mainctn.jpg
576 ms
ctn_title.gif
356 ms
nav.jpg
403 ms
menu2.jpg
610 ms
home.gif
533 ms
title.gif
690 ms
collosal.gif
562 ms
col.jpg
1202 ms
getstats.php
347 ms
getstats.php
3760 ms
getstats.php
318 ms
getstats.php
339 ms
pmember_getstats.php
1774 ms
getstats.js.php
1635 ms
getstats.php
863 ms
pmember_getstats_cookie.js.php
524 ms
pmember_getstats_cookie.php
669 ms
getstats.php
592 ms
getstats.js.php
4942 ms
getstats.php
548 ms
getstats.js.php
640 ms
getstats.php
660 ms
getstats.php
615 ms
bg_footer.jpg
470 ms
colossal.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
colossal.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
colossal.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
JP
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Colossal.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed language. Our system also found out that Colossal.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
colossal.jp
Open Graph description is not detected on the main page of Colossal. 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: