5.5 sec in total
962 ms
4.3 sec
279 ms
Welcome to heartpocket.com homepage info - get ready to check Heartpocket best content right away, or after learning these important things about heartpocket.com
マグフレンズ・マグの相方 ハートポケット
Visit heartpocket.comWe analyzed Heartpocket.com page load time and found that the first response time was 962 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
heartpocket.com performance score
name
value
score
weighting
Value1.6 s
93/100
10%
Value5.9 s
14/100
25%
Value2.8 s
96/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.6 s
100/100
10%
962 ms
503 ms
355 ms
285 ms
281 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 34% of them (20 requests) were addressed to the original Heartpocket.com, 66% (39 requests) were made to Rakuten.ne.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Rakuten.ne.jp.
Page size can be reduced by 61.9 kB (10%)
605.8 kB
543.9 kB
In fact, the total size of Heartpocket.com main page is 605.8 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. 20% of websites need less resources to load. Images take 574.0 kB which makes up the majority of the site volume.
Potential reduce by 21.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.4 kB or 85% of the original size.
Potential reduce by 35.2 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. Heartpocket images are well optimized though.
Potential reduce by 613 B
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 613 B or 58% of the original size.
Potential reduce by 4.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. Heartpocket.com needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 85% of the original size.
Number of requests can be reduced by 7 (12%)
58
51
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Heartpocket. 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.
heartpocket.com
962 ms
top.css
503 ms
function.js
355 ms
spacer.gif
285 ms
menu_lineup.gif
281 ms
icon_fre_maru.jpg
283 ms
icon_fre_kaku.jpg
287 ms
icon_magfreA3.jpg
280 ms
icon_magAI.jpg
285 ms
icon_magAI_600A.jpg
531 ms
icon_magAI_roll.jpg
545 ms
menu_friend2.jpg
691 ms
menu_aikata.jpg
840 ms
menu_recovo.gif
543 ms
m_fre_maru_wh90.jpg
551 ms
m_fre_maru_pi90.jpg
1123 ms
m_fre_maru_bl90.jpg
958 ms
m_fre_maru_gr90.jpg
1123 ms
m_fre_maru_red90.jpg
982 ms
m_fre_maru_ye90.jpg
957 ms
m_fre_kaku_wh90.jpg
1093 ms
m_fre_kaku_pi90.jpg
1221 ms
m_fre_kaku_bl90.jpg
1216 ms
m_fre_kaku_gr90.jpg
1248 ms
m_fre_kaku_red90.jpg
1342 ms
m_fre_kaku_ye90.jpg
1540 ms
m_fre_A4_wh90.jpg
1524 ms
m_fre_A4_ow90.jpg
1620 ms
m_fre_A4_NWS-Y90.jpg
1632 ms
m_fre_A4_NWS-W90.jpg
1507 ms
m_fre_A4_NWS-G90.jpg
1760 ms
m_fre_A3_wh90.jpg
1908 ms
m_fre_A3_ow90.jpg
1781 ms
m_fre_A3_NWS-Y90.jpg
1951 ms
m_fre_A3_NWS-W90.jpg
2019 ms
m_fre_A3_NWS-G90.jpg
2035 ms
img_magAI_200_90.jpg
2173 ms
img_magAI_300_90.jpg
2028 ms
img_magAI_roll_90.jpg
2165 ms
logo.gif
160 ms
headnavi1.gif
169 ms
headnavi2.gif
177 ms
headnavi3.gif
313 ms
navi_01.jpg
337 ms
navi_02.jpg
509 ms
navi_03.jpg
508 ms
navi_04.jpg
352 ms
navi_05.jpg
352 ms
ickicon15.gif
465 ms
top_02.jpg
1006 ms
top_01.jpg
1403 ms
magai_roll60.jpg
2556 ms
magai_roll90.jpg
2765 ms
magai_rollwm.jpg
2627 ms
navi_01_on.jpg
155 ms
navi_02_on.jpg
169 ms
navi_03_on.jpg
179 ms
navi_04_on.jpg
171 ms
navi_05_on.jpg
172 ms
heartpocket.com accessibility score
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
Links do not have a discernible name
heartpocket.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
heartpocket.com 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
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Heartpocket.com 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 Heartpocket.com main page’s claimed encoding is shift_jis. 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.
heartpocket.com
Open Graph description is not detected on the main page of Heartpocket. 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: