Tools & Wizards About Us
camio.jp screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

camio.jp

『上大岡ショッピングゾーン－camio カミオ』の公式ホームページ

Page Load Speed

5 sec in total

First Response

864 ms

Resources Loaded

3.9 sec

Page Rendered

228 ms

camio.jp screenshot

About Website

Visit camio.jp now to see the best up-to-date Camio content for Japan and also check out these interesting facts you probably never knew about camio.jp

京急本線・上大岡駅にあるショッピングセンター上大岡ショッピングゾーン－camio カミオの公式サイト

Visit camio.jp

Key Findings

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

Performance Metrics

camio.jp performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value7.5 s

48/100

10%

Network Requests Diagram

camio.jp

864 ms

common.css

325 ms

top.css

330 ms

nivo-slider.css

391 ms

jquery.min.js

10 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 95% of them (42 requests) were addressed to the original Camio.jp, 2% (1 request) were made to Ajax.googleapis.com and 2% (1 request) 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 Camio.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.5 kB (11%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-90%

Potential reduce by 28.2 kB

  • Original 31.3 kB
  • After minification 9.8 kB
  • After compression 3.1 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 21.5 kB, which is 69% 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 28.2 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 52.1 kB

  • Original 1.5 MB
  • After minification 1.4 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. Camio images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 89.6 kB

  • Original 127.7 kB
  • After minification 113.0 kB
  • After compression 38.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 89.6 kB or 70% of the original size.

CSS Optimization

-75%

Potential reduce by 9.6 kB

  • Original 12.8 kB
  • After minification 9.1 kB
  • After compression 3.2 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. Camio.jp needs all CSS files to be minified and compressed as it can save up to 9.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (12%)

Requests Now

42

After Optimization

37

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Camio. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

camio.jp

camio.jp

864 ms

common.css

common.css

325 ms

top.css

top.css

330 ms

nivo-slider.css

nivo-slider.css

391 ms

jquery.min.js

jquery.min.js

10 ms

jquery.cookie.js

jquery.cookie.js

390 ms

jquery.textchange.js

jquery.textchange.js

414 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

685 ms

sp.js

sp.js

486 ms

js

js

62 ms

site_background.jpg

site_background.jpg

984 ms

btn_font_s.png

btn_font_s.png

196 ms

btn_font_m.png

btn_font_m.png

165 ms

btn_font_l.png

btn_font_l.png

199 ms

pc_logo.png

pc_logo.png

238 ms

menu1.jpg

menu1.jpg

332 ms

menu3.jpg

menu3.jpg

391 ms

menu4.jpg

menu4.jpg

398 ms

menu2.jpg

menu2.jpg

400 ms

menu5.jpg

menu5.jpg

503 ms

icn_parking_available.jpg

icn_parking_available.jpg

495 ms

menu6-2.jpg

menu6-2.jpg

585 ms

menu6-3.jpg

menu6-3.jpg

595 ms

camio_slide001.jpg

camio_slide001.jpg

1691 ms

camio_slide002.jpg

camio_slide002.jpg

2137 ms

nav_top1.jpg

nav_top1.jpg

732 ms

nav_top2.jpg

nav_top2.jpg

780 ms

nav_top3.jpg

nav_top3.jpg

794 ms

nav_top4.jpg

nav_top4.jpg

960 ms

cap_news.jpg

cap_news.jpg

1946 ms

btn_access.jpg

btn_access.jpg

992 ms

btn_access.jpg

btn_access.jpg

1189 ms

btn_parking.jpg

btn_parking.jpg

1178 ms

btn_parking.jpg

btn_parking.jpg

1190 ms

btn_parking3.jpg

btn_parking3.jpg

1376 ms

btn_contact.jpg

btn_contact.jpg

1418 ms

img_contact.jpg

img_contact.jpg

1783 ms

btn_contact_form.jpg

btn_contact_form.jpg

1572 ms

bg_wrapper.jpg

bg_wrapper.jpg

2485 ms

loading.gif

loading.gif

1466 ms

btn_font_m_ov.png

btn_font_m_ov.png

1521 ms

btn_font_m_ov_ov.png

btn_font_m_ov_ov.png

1636 ms

arrows.png

arrows.png

1652 ms

bullets.png

bullets.png

1683 ms

Accessibility Review

camio.jp accessibility score

77

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

Image elements do not have [alt] attributes

Best Practices

camio.jp best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

camio.jp SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

camio.jp

Open Graph description is not detected on the main page of Camio. 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: