7.2 sec in total
962 ms
5.9 sec
281 ms
Welcome to 2626.co.jp homepage info - get ready to check 2626 best content for Japan right away, or after learning these important things about 2626.co.jp
DAIGOさんでおなじみのアリさんマークの引越社です。無料でお見積もりいたします!家族引越し、単身引越し、オフィス引越しなど、住まいのご変更は、年間30万件の引っ越し実績と、安心引越しを提供する身元保障制度導入の引っ越し業者【アリさんマークの引越社】にお任せください。
Visit 2626.co.jpWe analyzed 2626.co.jp page load time and found that the first response time was 962 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
2626.co.jp performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value11.9 s
0/100
25%
Value10.7 s
7/100
10%
Value130 ms
96/100
30%
Value0.111
87/100
15%
Value11.5 s
18/100
10%
962 ms
334 ms
508 ms
349 ms
2285 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 69% of them (82 requests) were addressed to the original 2626.co.jp, 6% (7 requests) were made to Apis.google.com and 4% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain 2626.co.jp.
Page size can be reduced by 279.7 kB (51%)
543.7 kB
264.0 kB
In fact, the total size of 2626.co.jp main page is 543.7 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. 50% of websites need less resources to load. Javascripts take 287.3 kB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 76% of the original size.
Potential reduce by 6.1 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. 2626 images are well optimized though.
Potential reduce by 169.1 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 169.1 kB or 59% of the original size.
Potential reduce by 71.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. 2626.co.jp needs all CSS files to be minified and compressed as it can save up to 71.5 kB or 86% of the original size.
Number of requests can be reduced by 55 (48%)
115
60
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2626. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
2626.co.jp
962 ms
screen.css
334 ms
swfobject2.js
508 ms
link_bana.css
349 ms
jquery-1.7.2.min.js
2285 ms
swapimage.js
361 ms
common.js
499 ms
__utm.js
733 ms
plusone.js
89 ms
clen.css
354 ms
common.css
209 ms
layout.css
499 ms
module.css
2024 ms
bookmark_button.js
318 ms
widgets.js
4 ms
Trace
584 ms
ip2c.js
352 ms
conversion.js
17 ms
cb=gapi.loaded_0
41 ms
button-only.gif
159 ms
__utm.gif
180 ms
bg_body.jpg
177 ms
img_logo.gif
181 ms
bg_tagline.jpg
175 ms
img_tel.gif
167 ms
ico_popup_arrow_w.gif
170 ms
gn_family_df.gif
333 ms
gn_single_df.gif
338 ms
gn_long_df.gif
347 ms
gn_estimate_df.gif
352 ms
gt_non_flash.jpg
708 ms
h2_gt_plan.gif
362 ms
btn_gt_family_df.gif
500 ms
btn_gt_single_df.gif
675 ms
btn_gt_long_df.gif
521 ms
h2_gt_calendar.gif
528 ms
h2_gt_news.gif
540 ms
ico_news_news.gif
666 ms
ico_news_store.gif
694 ms
ico_news_campaign.gif
706 ms
bana.gif
720 ms
h2_gt_mobile_info.gif
831 ms
img_mobile_logo.gif
843 ms
img_gt_mobile_qr.gif
866 ms
h2_gt_child110.gif
879 ms
h2_estimate.jpg
881 ms
h3_newestimate01.gif
901 ms
img_newestimate01.gif
1012 ms
img_newestimate02.gif
1025 ms
img_newestimate03.gif
1046 ms
h3_newestimate02.gif
1055 ms
h3_newestimate03.gif
1074 ms
h3_newestimate04.gif
1081 ms
img_newestimate04.gif
1161 ms
btn_newestimate01_df.gif
1189 ms
h2_tel.gif
1189 ms
252 ms
VLJavaScript_fp1fp2bs.js
785 ms
like.php
72 ms
img_tel_subnavi.gif
1069 ms
170x56.jpg
1068 ms
37_170X65.gif
1093 ms
btn_campaign_df.gif
1159 ms
btn_knowhow_df.gif
1181 ms
btn_policy_df.gif
1218 ms
vpc6VNjRPXV.js
295 ms
LVx-xkvaJ0b.png
333 ms
btn_mansion_df.gif
1079 ms
h2_service.gif
1076 ms
logo_junvie.gif
1100 ms
reset.css
11 ms
entry-button.css
12 ms
logo_photomail.gif
1144 ms
logo_introduction.jpg
1333 ms
button-counter.gif
5 ms
logo_affiliate.gif
1071 ms
logo_hikkoshimail.gif
1067 ms
logo_chintai.gif
1062 ms
logo_ana.gif
1085 ms
logo_jal.gif
998 ms
bg_fontsize.gif
1070 ms
img_fontsize.gif
1071 ms
bg_font_s.gif
1059 ms
bg_font_m.gif
1097 ms
bg_font_l.gif
1109 ms
bg_dotted_line.gif
1031 ms
ico_blue_arrow.gif
1072 ms
bg_sn_estimate_foot.gif
1073 ms
bg_sn_body.gif
1064 ms
bg_sn_middle.gif
1102 ms
Trace
394 ms
ga.js
30 ms
ico_popup_arrow.gif
1093 ms
__utm.gif
40 ms
ip2c.php
1068 ms
__utm.gif
35 ms
analytics.js
34 ms
67 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
59 ms
cb=gapi.loaded_1
32 ms
fastbutton
107 ms
collect
24 ms
postmessageRelay
81 ms
bg_sn_foot.gif
1005 ms
107 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
30 ms
cb=gapi.loaded_0
34 ms
cb=gapi.loaded_1
50 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
107 ms
api.js
64 ms
core:rpc:shindig.random:shindig.sha1.js
88 ms
2536007149-postmessagerelay.js
71 ms
jot
99 ms
txtM.css
179 ms
txtS.css
178 ms
txtL.css
179 ms
print.css
178 ms
bana2.png
179 ms
2626.co.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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
2626.co.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
2626.co.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
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 2626.co.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 2626.co.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.
2626.co.jp
Open Graph description is not detected on the main page of 2626. 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: