19.9 sec in total
1.4 sec
18 sec
567 ms
Visit localchara.jp now to see the best up-to-date Localchara content for Japan and also check out these interesting facts you probably never knew about localchara.jp
ご当地キャラカタログは、ご当地キャラ・ゆるキャラ®・ローカルヒーローなどの地域性のあるキャラクター情報を、ユーザーが自由に投稿・評価できるカタログサイトです。
Visit localchara.jpWe analyzed Localchara.jp page load time and found that the first response time was 1.4 sec and then it took 18.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
localchara.jp performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value9.2 s
1/100
25%
Value7.7 s
25/100
10%
Value2,640 ms
4/100
30%
Value0.052
99/100
15%
Value16.7 s
5/100
10%
1390 ms
749 ms
1437 ms
113 ms
1976 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 37% of them (66 requests) were addressed to the original Localchara.jp, 6% (11 requests) were made to Maps.google.com and 5% (9 requests) were made to Plugins.mixi.jp. The less responsive or slowest element that took the longest time to load (8.8 sec) relates to the external source Cre.adjust-net.jp.
Page size can be reduced by 1.4 MB (59%)
2.3 MB
950.2 kB
In fact, the total size of Localchara.jp main page is 2.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. 70% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 63.6 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 63.6 kB or 76% of the original size.
Potential reduce by 33.0 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. Localchara images are well optimized though.
Potential reduce by 975.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 975.8 kB or 66% of the original size.
Potential reduce by 290.7 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. Localchara.jp needs all CSS files to be minified and compressed as it can save up to 290.7 kB or 82% of the original size.
Number of requests can be reduced by 92 (55%)
166
74
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Localchara. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
localchara.jp
1390 ms
localchara.css
749 ms
sidebar.css
1437 ms
jsapi
113 ms
jquery.scrollTo-1.4.2-min.js
1976 ms
jquery.exflexfixed-0.3.0.js
465 ms
jquery.tipsy.js
504 ms
tipsy.css
1280 ms
document-ready.js
5847 ms
jquery-ui.css
95 ms
toppage.css
1490 ms
jquery.cookie.js
1005 ms
js
153 ms
google.map.manager.js
1261 ms
remove_action.js
1475 ms
event.css
1309 ms
widgets.js
231 ms
bookmark_button.js
555 ms
sh.adingo.jp
753 ms
ads_premium.js
877 ms
jquery.min.js
113 ms
ga.js
190 ms
jquery-ui.min.js
118 ms
logo.png
436 ms
button-only.gif
207 ms
sp00302298_4f73733983a40d799f002c38efb65b6c.png
2175 ms
help.gif
209 ms
4d490658a0ac5.gif
2082 ms
4d33f09e1ba2b.jpg
2477 ms
4d596ae833fe8.jpg
728 ms
520c21ba9447f.jpg
500 ms
5705c3f60014c.jpg
650 ms
5704c5834755d.png
1683 ms
56f549d811698.png
2538 ms
56e60ad0c7283.jpg
2474 ms
sch_key.png
1890 ms
sch_place.png
1897 ms
sch_tag.png
2470 ms
568529ea25ff2.jpg
2733 ms
56f2b8a8d2cee.png
3141 ms
5500183b53313.jpg
2727 ms
54d59fb854e86.gif
2953 ms
53aa53f4e7cd4.jpg
2919 ms
5383038cd7af4.jpg
2859 ms
53951caa18220.jpg
3140 ms
56eb617acf9c2.jpg
2939 ms
56e517113d128.jpg
3138 ms
56b07913e64be.jpg
3322 ms
56a2f6238ef2b.jpg
3321 ms
51435db272e95.jpg
3323 ms
4d52700618356.jpg
3444 ms
55f9fc5733e9f.jpg
3588 ms
55d4865c83cce.jpg
3443 ms
55cabd5f0e69f.jpg
3444 ms
5460daf87b46e.jpg
4210 ms
line_banner.jpg
4025 ms
local_business.gif
5642 ms
kyoukai_270_85.gif
6225 ms
pagetop.png
3656 ms
sdk.js
1968 ms
top_l.png
3750 ms
top_r.png
3933 ms
favorite.pl
527 ms
share
471 ms
__utm.gif
103 ms
363 ms
sync
1683 ms
sync
585 ms
pixel
373 ms
cm
4156 ms
sync
575 ms
sync
1333 ms
jstag
278 ms
i.adingo.jp
1348 ms
dot.png
3830 ms
naname.png
3710 ms
round160.png
3725 ms
jquery-1.7.2.min.js
159 ms
pixel
61 ms
mixi_check_entry.css
1095 ms
errorreport.production.js
3558 ms
json.js
3757 ms
underscore-string-1.3.3-2.0.0-compress.js
3772 ms
namespace-brook-compress.js
3758 ms
prototype-effects-1.6.1-1.8.3-compress.js
1010 ms
mixi.js
2858 ms
plugins.js
1308 ms
favorite.production.js
1481 ms
jquery-1.7.1.min-noconflict-compress.js
7408 ms
863 ms
arw_more.gif
3527 ms
829 ms
btn_iine_20.png
1469 ms
sch_base.png
4605 ms
1976 ms
acj
84 ms
pd
149 ms
ads.js
649 ms
ri
109 ms
9ab9c3fd-db3e-e852-75f5-7396ef8df3d8
422 ms
pixel
116 ms
sd
41 ms
sd
108 ms
sd
44 ms
ads
254 ms
186 ms
sd
95 ms
sd
69 ms
white_grade.png
2747 ms
2024104.jpg
8845 ms
pixel
72 ms
ITayXa6a1FQ
322 ms
impbcn
687 ms
adcore.js
260 ms
adcore_pc.js
267 ms
cookiemapping
1935 ms
cookiemapping
2401 ms
round150.png
3272 ms
round_t_l.png
2561 ms
adcore_pc_inline.js
113 ms
round_t_r.png
2568 ms
www-embed-player-vfl5foy2V.css
775 ms
www-embed-player.js
929 ms
820 ms
xd_arbiter.php
591 ms
xd_arbiter.php
856 ms
ad_spot.aspx
746 ms
ui-bg_flat_75_ffffff_40x100.png
219 ms
common.js
154 ms
map.js
154 ms
button.71000885400e222c3c0eec823f8f93f0.js
442 ms
ui-icons_222222_256x240.png
229 ms
StaticMapService.GetMapImage
279 ms
879 ms
help
2851 ms
help
2465 ms
help
2763 ms
arw_pink.gif
2895 ms
util.js
506 ms
onion.js
138 ms
ViewportInfoService.GetViewportInfo
92 ms
stats.js
113 ms
controls.js
176 ms
round_u_l.png
3155 ms
round_u_r.png
3292 ms
transparent.png
101 ms
vt
89 ms
vt
56 ms
like.php
237 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
91 ms
style.css
390 ms
ad_creative.ashx
3141 ms
9aKOW9kHIBrJTB9ONj-e1oyTZuOGlgCE-J5p-KupNmo.js
403 ms
ad_status.js
402 ms
index.php
3436 ms
3XaI8mzWBSs.js
2607 ms
LVx-xkvaJ0b.png
2708 ms
jot
602 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
497 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
562 ms
AuthenticationService.Authenticate
400 ms
css
243 ms
google4.png
185 ms
mapcnt6.png
177 ms
sv5.png
614 ms
jot
524 ms
vt
146 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
231 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
346 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
435 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
435 ms
analytics.js
49 ms
comment001.gif
60 ms
marker.js
44 ms
map.png
203 ms
favorite_button003-.png
350 ms
comment_content_top001.gif
84 ms
QuotaService.RecordEvent
51 ms
RestoreXidToMediaStorage.html
346 ms
localchara.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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
localchara.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
Page has valid source maps
localchara.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Localchara.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 Localchara.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.
localchara.jp
Open Graph data is detected on the main page of Localchara. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: