15.3 sec in total
6.4 sec
8.6 sec
316 ms
Visit cre.jp now to see the best up-to-date Cre content for Japan and also check out these interesting facts you probably never knew about cre.jp
創作者のためのネットワークサービスを提供します。
Visit cre.jpWe analyzed Cre.jp page load time and found that the first response time was 6.4 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cre.jp performance score
name
value
score
weighting
Value7.6 s
1/100
10%
Value9.5 s
0/100
25%
Value34.4 s
0/100
10%
Value1,250 ms
19/100
30%
Value0.043
99/100
15%
Value21.0 s
1/100
10%
6353 ms
18 ms
396 ms
373 ms
385 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 64% of them (35 requests) were addressed to the original Cre.jp, 11% (6 requests) were made to Ecx.images-amazon.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Cre.jp.
Page size can be reduced by 1.3 MB (71%)
1.8 MB
533.0 kB
In fact, the total size of Cre.jp main page is 1.8 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. Javascripts take 771.3 kB which makes up the majority of the site volume.
Potential reduce by 118.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 118.3 kB or 82% of the original size.
Potential reduce by 20.9 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. Cre images are well optimized though.
Potential reduce by 587.0 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 587.0 kB or 76% of the original size.
Potential reduce by 573.5 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. Cre.jp needs all CSS files to be minified and compressed as it can save up to 573.5 kB or 86% of the original size.
Number of requests can be reduced by 39 (76%)
51
12
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
cre.jp
6353 ms
ga.js
18 ms
wp-emoji-release.min.js
396 ms
widget.css
373 ms
bootstrap.custom.css
385 ms
public.css
396 ms
style.css
796 ms
style.css
1653 ms
style.css
557 ms
font-awesome.css
575 ms
animations.css
595 ms
media.css
587 ms
ipad.css
744 ms
jquery.js
959 ms
jquery-migrate.min.js
782 ms
counter.css
800 ms
twitpic.css
930 ms
__utm.gif
14 ms
css
26 ms
css
38 ms
ads.js
171 ms
ads.js
155 ms
colorbox.css
793 ms
styles.css
808 ms
bootstrap.min.js
822 ms
bootstrap-paginator.min.js
931 ms
public.js
963 ms
comment-reply.min.js
986 ms
modernizr-min.js
1008 ms
jquery.carouFredSel-6.2.1-min.js
1028 ms
jquery.cycle.js
1118 ms
jquery.prettyPhoto-min.js
1152 ms
jquery.flexslider-min.js
1182 ms
jquery.fitvids-min.js
1206 ms
main.js
1655 ms
jquery.colorbox-min.js
1304 ms
custom.js
1340 ms
2015022615-3.png
211 ms
2015022615-31.png
197 ms
ads-common.js
254 ms
icomoon.woff
187 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
6 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
19 ms
8c9q46CAcsp9TiRX9KLgZC3USBnSvpkopQaUR-2r7iU.ttf
20 ms
cm
279 ms
cm
239 ms
41DDTIONHJL._SL50_.jpg
61 ms
149 ms
overlay.png
211 ms
51C9R6T0GpL._SL50_.jpg
57 ms
155 ms
315WIkUykpL._SX60_SY80_.jpg
56 ms
51f-5D90E+L._SX60_SY80_.jpg
11 ms
thumb-no-image._SX60_SY80_.jpg
37 ms
51QjtAjojZL._SX60_SY80_.jpg
58 ms
cre.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
cre.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
cre.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cre.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 Cre.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.
cre.jp
Open Graph description is not detected on the main page of Cre. 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: