Tools & Wizards About Us
2626.co.jp screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

2626.co.jp

【公式最安】アリさんマークの引越社｜

Page Load Speed

8.8 sec in total

First Response

568 ms

Resources Loaded

7.4 sec

Page Rendered

861 ms

2626.co.jp screenshot

About Website

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.jp

Key Findings

We analyzed 2626.co.jp page load time and found that the first response time was 568 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

2626.co.jp performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.637

9/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

2626.co.jp

568 ms

www.2626.co.jp

1651 ms

jquery-ui.css

823 ms

jquery.fancybox.css

710 ms

slick.css

536 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 88% of them (104 requests) were addressed to the original 2626.co.jp, 5% (6 requests) were made to Google.com and 3% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain 2626.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (24%)

Content Size

5.8 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 2626.co.jp main page is 5.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. 70% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.0 kB

  • Original 103.8 kB
  • After minification 98.1 kB
  • After compression 17.8 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 86.0 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 146.0 kB

  • Original 4.0 MB
  • After minification 3.9 MB

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.

JavaScript Optimization

-67%

Potential reduce by 819.7 kB

  • Original 1.2 MB
  • After minification 987.5 kB
  • After compression 400.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 819.7 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 349.4 kB

  • Original 411.4 kB
  • After minification 346.4 kB
  • After compression 62.0 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 349.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (32%)

Requests Now

116

After Optimization

79

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 116 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 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

2626.co.jp

2626.co.jp

568 ms

www.2626.co.jp

www.2626.co.jp

1651 ms

jquery-ui.css

jquery-ui.css

823 ms

jquery.fancybox.css

jquery.fancybox.css

710 ms

slick.css

slick.css

536 ms

style.css

style.css

1424 ms

style.css

style.css

565 ms

head.js

head.js

708 ms

style.min.css

style.min.css

1410 ms

styles.css

styles.css

581 ms

styles.css

styles.css

712 ms

jquery.min.js

jquery.min.js

1237 ms

jquery-migrate.min.js

jquery-migrate.min.js

768 ms

js

js

85 ms

cse.js

cse.js

55 ms

jquery.min.js

jquery.min.js

924 ms

slick.js

slick.js

1019 ms

jquery.dotdotdot.js

jquery.dotdotdot.js

737 ms

jquery-ui.js

jquery-ui.js

2455 ms

jquery.fancybox.js

jquery.fancybox.js

1423 ms

common.js

common.js

1243 ms

infiniteslidev2.js

infiniteslidev2.js

1242 ms

js

js

44 ms

index.js

index.js

1103 ms

index.js

index.js

1104 ms

jquery.form.min.js

jquery.form.min.js

1246 ms

scripts.js

scripts.js

1247 ms

logo.png

logo.png

312 ms

img01.png

img01.png

312 ms

pop_img01.png

pop_img01.png

485 ms

pop_img02.png

pop_img02.png

483 ms

pop_img03.png

pop_img03.png

484 ms

img02.png

img02.png

487 ms

img03.png

img03.png

509 ms

img04.png

img04.png

658 ms

img05.png

img05.png

659 ms

img06.png

img06.png

660 ms

menu.png

menu.png

661 ms

close02.png

close02.png

673 ms

img15.png

img15.png

832 ms

tel02.png

tel02.png

833 ms

icon09_out.png

icon09_out.png

832 ms

img20.png

img20.png

835 ms

img16.png

img16.png

836 ms

img17.png

img17.png

1007 ms

img18.png

img18.png

1008 ms

img19.png

img19.png

1008 ms

main_img07.jpg

main_img07.jpg

1188 ms

sp_main_img07.jpg

sp_main_img07.jpg

1332 ms

main_img05.jpg

main_img05.jpg

1707 ms

sp_main_img05.jpg

sp_main_img05.jpg

1599 ms

main_img02.jpg

main_img02.jpg

1182 ms

sp_main_img02.jpg

sp_main_img02.jpg

1358 ms

main_img08.jpg

main_img08.jpg

1893 ms

sp_main_img08.jpg

sp_main_img08.jpg

1630 ms

main_img03.jpg

main_img03.jpg

1577 ms

sp_main_img03.jpg

sp_main_img03.jpg

1439 ms

prev02.png

prev02.png

1578 ms

cse_element__en.js

cse_element__en.js

96 ms

default+en.css

default+en.css

134 ms

default.css

default.css

137 ms

next02.png

next02.png

1504 ms

photo04.png

photo04.png

1577 ms

photo01.jpg

photo01.jpg

1566 ms

photo05.png

photo05.png

1606 ms

photo02.jpg

photo02.jpg

1609 ms

photo06.png

photo06.png

1601 ms

photo15.jpg

photo15.jpg

1721 ms

%E5%BC%95%E8%B6%8A%E6%BA%96%E5%82%99-%E3%83%AF%E3%83%BC%E3%83%89%E3%83%97%E3%83%AC%E3%82%B9%E7%94%A8.jpg

%E5%BC%95%E8%B6%8A%E6%BA%96%E5%82%99-%E3%83%AF%E3%83%BC%E3%83%89%E3%83%97%E3%83%AC%E3%82%B9%E7%94%A8.jpg

1751 ms

%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B302.jpg

%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B302.jpg

1590 ms

%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B303.jpg

%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B303.jpg

1781 ms

%E7%B4%B9%E4%BB%8B%E3%83%97%E3%83%AC%E3%82%BC%E3%83%B3%E3%83%88%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3-723%C3%97389%EF%BC%88%E3%82%A2%E3%83%AA%E3%83%83%E3%82%AF%E3%82%B9%EF%BC%89.jpg

%E7%B4%B9%E4%BB%8B%E3%83%97%E3%83%AC%E3%82%BC%E3%83%B3%E3%83%88%E3%82%AD%E3%83%A3%E3%83%B3%E3%83%9A%E3%83%BC%E3%83%B3-723%C3%97389%EF%BC%88%E3%82%A2%E3%83%AA%E3%83%83%E3%82%AF%E3%82%B9%EF%BC%89.jpg

1761 ms

photo04.jpg

photo04.jpg

1475 ms

photo05.jpg

photo05.jpg

1593 ms

photo06.jpg

photo06.jpg

1661 ms

photo07.jpg

photo07.jpg

1707 ms

icon01.png

icon01.png

1738 ms

icon02.png

icon02.png

1597 ms

photo09.png

photo09.png

1609 ms

sp_photo03.png

sp_photo03.png

1612 ms

photo07.png

photo07.png

1672 ms

photo08.png

photo08.png

1696 ms

photo09.png

photo09.png

1577 ms

photo10.png

photo10.png

1597 ms

photo11.png

photo11.png

1607 ms

photo12.png

photo12.png

1436 ms

js_photo08.jpg

js_photo08.jpg

1508 ms

js_photo09.jpg

js_photo09.jpg

1365 ms

js_photo10.jpg

js_photo10.jpg

1402 ms

js

js

160 ms

async-ads.js

async-ads.js

153 ms

branding.png

branding.png

149 ms

clear.png

clear.png

154 ms

nav_logo114.png

nav_logo114.png

154 ms

js

js

130 ms

analytics.js

analytics.js

124 ms

js_photo11.jpg

js_photo11.jpg

1221 ms

com_slide_ansin.jpg

com_slide_ansin.jpg

1190 ms

com_slide_kansen.jpg

com_slide_kansen.jpg

1192 ms

collect

collect

14 ms

com_slide_line.jpg

com_slide_line.jpg

1177 ms

com_slide_junvie_02.jpg

com_slide_junvie_02.jpg

1154 ms

com_slide_saiyou.jpg

com_slide_saiyou.jpg

1198 ms

com_slide_sdgs.jpg

com_slide_sdgs.jpg

1217 ms

com_slide_ukraine.jpg

com_slide_ukraine.jpg

1215 ms

com_slide_nophotos.jpg

com_slide_nophotos.jpg

1098 ms

tel03.png

tel03.png

1143 ms

img07.png

img07.png

1176 ms

img08.png

img08.png

1198 ms

img09.png

img09.png

1218 ms

img10.png

img10.png

1201 ms

pagetop.png

pagetop.png

1075 ms

tel.png

tel.png

1061 ms

bg01.png

bg01.png

1059 ms

icon03.png

icon03.png

1054 ms

icon01.png

icon01.png

1063 ms

prev01.png

prev01.png

1054 ms

next01.png

next01.png

1054 ms

Accessibility Review

2626.co.jp accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

2626.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

2626.co.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: