Tools & Wizards About Us
kitamura.jp screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

kitamura.jp

カメラのキタムラ｜新品・中古カメラやレンズの販売から買取まで

Page Load Speed

22.4 sec in total

First Response

17 ms

Resources Loaded

21.9 sec

Page Rendered

470 ms

kitamura.jp screenshot

About Website

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

写真現像やカメラ・デジカメの販売、買取などはカメラのキタムラへ。あなたの大切なお写真の現像・保存・プリントも写真専門店カメラのキタムラにお任せ下さい。スマホも格安で販売中です。

Visit kitamura.jp

Key Findings

We analyzed Kitamura.jp page load time and found that the first response time was 17 ms and then it took 22.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

kitamura.jp performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value2,640 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.42

23/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

kitamura.jp

17 ms

www.kitamura.jp

31 ms

common.css

705 ms

a1c1a8cc15.js

59 ms

typicons.css

27 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 69% of them (59 requests) were addressed to the original Kitamura.jp, 6% (5 requests) were made to Googletagmanager.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Member.kitamura.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 148.8 kB (14%)

Content Size

1.1 MB

After Optimization

935.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kitamura.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. 70% of websites need less resources to load. Images take 710.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 96.3 kB

  • Original 116.9 kB
  • After minification 110.3 kB
  • After compression 20.6 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 96.3 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 25.7 kB

  • Original 710.6 kB
  • After minification 684.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. Kitamura images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 25.3 kB

  • Original 233.7 kB
  • After minification 233.5 kB
  • After compression 208.4 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 25.3 kB or 11% of the original size.

CSS Optimization

-6%

Potential reduce by 1.5 kB

  • Original 22.5 kB
  • After minification 22.5 kB
  • After compression 21.1 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. Kitamura.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 50 (60%)

Requests Now

83

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kitamura.jp

kitamura.jp

17 ms

www.kitamura.jp

www.kitamura.jp

31 ms

common.css

common.css

705 ms

a1c1a8cc15.js

a1c1a8cc15.js

59 ms

typicons.css

typicons.css

27 ms

swiper.min.css

swiper.min.css

34 ms

local.css

local.css

16 ms

jquery.js

jquery.js

729 ms

jquery-ui.min.js

jquery-ui.min.js

748 ms

device_switch.js

device_switch.js

22 ms

smoothScroll.js

smoothScroll.js

749 ms

response.min.js

response.min.js

746 ms

util_new.js

util_new.js

727 ms

jquery.sbm.js

jquery.sbm.js

1400 ms

urchin.js

urchin.js

1440 ms

tracker.js

tracker.js

748 ms

dropdown.js

dropdown.js

749 ms

swiper.jquery.min.js

swiper.jquery.min.js

747 ms

jquery.inview.min.js

jquery.inview.min.js

748 ms

isotope.js

isotope.js

749 ms

packery-mode.pkgd.js

packery-mode.pkgd.js

766 ms

local.js

local.js

766 ms

common.js

common.js

1517 ms

conversion.js

conversion.js

90 ms

developers.line.biz

developers.line.biz

861 ms

gtm.js

gtm.js

464 ms

fbds.js

fbds.js

167 ms

login-button.html

login-button.html

20283 ms

__utm.gif

__utm.gif

145 ms

logo_h_kitamura.png

logo_h_kitamura.png

77 ms

logo_h_mario.png

logo_h_mario.png

75 ms

logo_sitekitamura.gif

logo_sitekitamura.gif

76 ms

btn_search_sp.png

btn_search_sp.png

76 ms

btn_regist_sp.png

btn_regist_sp.png

74 ms

btn_menu_sp.png

btn_menu_sp.png

161 ms

bg_gm_off.png

bg_gm_off.png

160 ms

btn_gm_01.png

btn_gm_01.png

161 ms

img_t.gif

img_t.gif

159 ms

btn_gm_02.png

btn_gm_02.png

160 ms

btn_gm_03.png

btn_gm_03.png

161 ms

btn_gm_04_rn.png

btn_gm_04_rn.png

190 ms

btn_gm_08.png

btn_gm_08.png

190 ms

btn_gm_06.png

btn_gm_06.png

188 ms

btn_gm_07.png

btn_gm_07.png

188 ms

cal_T_gwweekendsalebig.png

cal_T_gwweekendsalebig.png

188 ms

cal_T_uttoku_start.jpg

cal_T_uttoku_start.jpg

190 ms

jp_caroucel.jpg

jp_caroucel.jpg

194 ms

carousel_T_keyring.jpg

carousel_T_keyring.jpg

193 ms

carousel_T_watchsell.jpg

carousel_T_watchsell.jpg

205 ms

cal_T_new_used.jpg

cal_T_new_used.jpg

191 ms

img_t2x1.gif

img_t2x1.gif

189 ms

logo_f_c4_id.png

logo_f_c4_id.png

190 ms

fix_zensya_kaitori_pc.png

fix_zensya_kaitori_pc.png

194 ms

fix_zensya_kaitori_sp.png

fix_zensya_kaitori_sp.png

202 ms

like.php

like.php

464 ms

bg_flex_nav.png

bg_flex_nav.png

129 ms

img_nav_2.svg

img_nav_2.svg

131 ms

ico_sprite.png

ico_sprite.png

137 ms

bg_tPathHome.png

bg_tPathHome.png

55 ms

arrow_open_7x7.gif

arrow_open_7x7.gif

56 ms

img_sprite_ktmr.png

img_sprite_ktmr.png

57 ms

arrow_7x7.gif

arrow_7x7.gif

831 ms

283 ms

w9py8-RGams.js

w9py8-RGams.js

139 ms

FEppCFCt76d.png

FEppCFCt76d.png

249 ms

js

js

115 ms

analytics.js

analytics.js

233 ms

ytag.js

ytag.js

783 ms

destination

destination

234 ms

destination

destination

233 ms

destination

destination

231 ms

fbevents.js

fbevents.js

18 ms

huhbz069ij

huhbz069ij

423 ms

403 ms

pnl_M_shop.png

pnl_M_shop.png

135 ms

panel_A_apple.jpg

panel_A_apple.jpg

134 ms

pnl_M_gwweekendsalebig.png

pnl_M_gwweekendsalebig.png

730 ms

bn_A_watchsell.jpg

bn_A_watchsell.jpg

134 ms

linkid.js

linkid.js

180 ms

collect

collect

15 ms

clarity.js

clarity.js

16 ms

collect

collect

14 ms

ga-audiences

ga-audiences

63 ms

lt.js

lt.js

105 ms

err.gif

err.gif

663 ms

c.gif

c.gif

9 ms

Accessibility Review

kitamura.jp accessibility score

79

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.

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

kitamura.jp SEO score

91

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

High

Tap targets are not sized appropriately

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

kitamura.jp

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