8.2 sec in total
1.2 sec
6.6 sec
457 ms
Welcome to starheart.jp homepage info - get ready to check Star Heart best content for Japan right away, or after learning these important things about starheart.jp
名古屋の透視チャネラー/空(くう)のメッセンジャーMana(マナ)、名古屋市千種区のヒーリング・ラウンジStar Heart(スターハート)です。
Visit starheart.jpWe analyzed Starheart.jp page load time and found that the first response time was 1.2 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
starheart.jp performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value21.8 s
0/100
25%
Value18.5 s
0/100
10%
Value1,230 ms
20/100
30%
Value0.28
43/100
15%
Value19.8 s
2/100
10%
1168 ms
334 ms
698 ms
353 ms
6 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 69% of them (45 requests) were addressed to the original Starheart.jp, 5% (3 requests) were made to Platform.twitter.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Starheart.jp.
Page size can be reduced by 498.9 kB (47%)
1.1 MB
555.3 kB
In fact, the total size of Starheart.jp main page is 1.1 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. 45% of websites need less resources to load. Images take 432.7 kB which makes up the majority of the site volume.
Potential reduce by 24.4 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 24.4 kB or 73% of the original size.
Potential reduce by 40.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. Star Heart images are well optimized though.
Potential reduce by 197.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 197.3 kB or 65% of the original size.
Potential reduce by 236.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. Starheart.jp needs all CSS files to be minified and compressed as it can save up to 236.3 kB or 83% of the original size.
Number of requests can be reduced by 26 (42%)
62
36
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Star Heart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.starheart.jp
1168 ms
common.css
334 ms
style.css
698 ms
pagenavi-css.css
353 ms
jquery-1.8.3.js
6 ms
heightLine.js
528 ms
jquery.smoothScroll.js
663 ms
jquery.mobile-menu.js
510 ms
wp-emoji-release.min.js
530 ms
analytics.js
29 ms
sdk.js
300 ms
bg_point.png
533 ms
collect
11 ms
collect
150 ms
logo.png
336 ms
header_tel.png
209 ms
icon_menu.png
178 ms
lead.png
857 ms
default.png
831 ms
btn-list.png
385 ms
ef72cdeba6fd644352dcf0e51682efb1-250x354.jpg
994 ms
books-detail.png
666 ms
f3955587b0f65684f3ef7550128b1d0a-250x353.jpg
1112 ms
kaminagaranomichi.jpg
1148 ms
books_gold.gif
1364 ms
books_blue.gif
1489 ms
books_purple.gif
1194 ms
facebook.gif
1158 ms
btn_apply.png
1459 ms
f-logo.png
1324 ms
header_bg.png
1314 ms
menu-home_on.png
1354 ms
menu-prof.png
1479 ms
menu-seminar.png
1491 ms
menu-event.png
1530 ms
menu-movie.png
1524 ms
menu-blog.png
1623 ms
header_apply.png
1644 ms
bg.png
1645 ms
main_image.jpg
3111 ms
dotted_dashed.png
1691 ms
title_point.png
1703 ms
news_bg_repeat.png
1796 ms
news_bg_top.png
1808 ms
news_bg_btm.png
1808 ms
intro_title.png
2199 ms
footer_bg.png
1878 ms
pagetop.png
1969 ms
widgets.js
52 ms
bdRePSW6X80
143 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
20 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
28 ms
www-embed-player-vflQrT_sR.css
121 ms
www-embed-player.js
169 ms
base.js
286 ms
170 ms
xd_arbiter.php
216 ms
xd_arbiter.php
577 ms
jot
113 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
88 ms
ad_status.js
86 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
102 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
101 ms
jquery.mobile-menu.css
332 ms
sp.css
496 ms
starheart.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.
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
starheart.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
starheart.jp SEO score
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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Starheart.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 Starheart.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.
starheart.jp
Open Graph data is detected on the main page of Star Heart. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: