Tools & Wizards About Us
tiendeo.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

tiendeo.jp

近くのチラシ、クーポンや店舗情報 - Tiendeo (ティエンデオ)

Page Load Speed

3.9 sec in total

First Response

303 ms

Resources Loaded

3.1 sec

Page Rendered

469 ms

tiendeo.jp screenshot

About Website

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

お近くのスーパーやファッションショップのチラシやカタログ、また今いる場所から一番近い店舗の検索はTiendeo（ティエンデオ）におまかせ！

Visit tiendeo.jp

Key Findings

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

Performance Metrics

tiendeo.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

www.tiendeo.jp

303 ms

eb80d6e999f2bb25.css

73 ms

9152ea4b00ba8a30.css

77 ms

polyfills-c67a75d1b6f99dc8.js

126 ms

webpack-55e44a47e6c0dffc.js

151 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tiendeo.jp, 50% (27 requests) were made to Static-webapp.tiendeo.com and 46% (25 requests) were made to Static1.tiendeo.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Static1.tiendeo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.5 kB (9%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 147.8 kB

  • Original 185.7 kB
  • After minification 185.3 kB
  • After compression 38.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 147.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 2.7 kB

  • Original 1.0 MB
  • After minification 1.0 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. Tiendeo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 998 B

  • Original 484.3 kB
  • After minification 484.3 kB
  • After compression 483.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 49 B

  • Original 4.1 kB
  • After minification 4.1 kB
  • After compression 4.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. Tiendeo.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (40%)

Requests Now

53

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tiendeo. 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 as a result speed up the page load time.

Network Requests Diagram

www.tiendeo.jp

www.tiendeo.jp

303 ms

eb80d6e999f2bb25.css

eb80d6e999f2bb25.css

73 ms

9152ea4b00ba8a30.css

9152ea4b00ba8a30.css

77 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

126 ms

webpack-55e44a47e6c0dffc.js

webpack-55e44a47e6c0dffc.js

151 ms

framework-b5f5b57923c5a118.js

framework-b5f5b57923c5a118.js

155 ms

main-f2364aee791ed77e.js

main-f2364aee791ed77e.js

151 ms

_app-50100a3c5fb5e427.js

_app-50100a3c5fb5e427.js

164 ms

c78d26b1-a61fc8d5e94fcb7e.js

c78d26b1-a61fc8d5e94fcb7e.js

160 ms

8950-925590fa47143dd1.js

8950-925590fa47143dd1.js

154 ms

6782-a404136795ca722c.js

6782-a404136795ca722c.js

162 ms

4578-547bcc317256053f.js

4578-547bcc317256053f.js

162 ms

4613-4d6da91a3afd6caf.js

4613-4d6da91a3afd6caf.js

169 ms

4640-e496901e37bc7db1.js

4640-e496901e37bc7db1.js

170 ms

482-5cb99fd3e29efab8.js

482-5cb99fd3e29efab8.js

169 ms

8382-30b02ca20296e5ba.js

8382-30b02ca20296e5ba.js

173 ms

8098-fd54212f18ecad28.js

8098-fd54212f18ecad28.js

171 ms

5477-0535a17c8a094fba.js

5477-0535a17c8a094fba.js

173 ms

2065-3f58427d51dd0bb1.js

2065-3f58427d51dd0bb1.js

174 ms

729-4323c0ab7b9ce0f7.js

729-4323c0ab7b9ce0f7.js

173 ms

1102-b461c6e8a0e13697.js

1102-b461c6e8a0e13697.js

174 ms

4152-bfae025b1838dcc8.js

4152-bfae025b1838dcc8.js

175 ms

%5BcountryCode%5D-fd7be0d6f2d90d7f.js

%5BcountryCode%5D-fd7be0d6f2d90d7f.js

175 ms

_buildManifest.js

_buildManifest.js

178 ms

_ssgManifest.js

_ssgManifest.js

175 ms

LANDING

LANDING

415 ms

00001.jpg

00001.jpg

133 ms

logo-tiendeo-japan.png

logo-tiendeo-japan.png

70 ms

download-appstore.png

download-appstore.png

69 ms

download-googleplay.png

download-googleplay.png

67 ms

logo.png

logo.png

331 ms

00001.jpg

00001.jpg

502 ms

logo.png

logo.png

319 ms

00001.jpg

00001.jpg

582 ms

logo.png

logo.png

237 ms

00001.jpg

00001.jpg

516 ms

00001.jpg

00001.jpg

550 ms

00001.jpg

00001.jpg

507 ms

logo.png

logo.png

543 ms

00001.jpg

00001.jpg

702 ms

logo.png

logo.png

701 ms

00001.jpg

00001.jpg

698 ms

logo.png

logo.png

727 ms

00001.jpg

00001.jpg

745 ms

00001.jpg

00001.jpg

761 ms

00001.jpg

00001.jpg

1080 ms

00001.jpg

00001.jpg

703 ms

logo.png

logo.png

886 ms

logo2.png

logo2.png

2436 ms

logo2.png

logo2.png

953 ms

logo2.png

logo2.png

928 ms

logo2.png

logo2.png

959 ms

logo2.png

logo2.png

914 ms

logo2.png

logo2.png

1103 ms

Accessibility Review

tiendeo.jp accessibility score

100

Accessibility Issues

Best Practices

tiendeo.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

tiendeo.jp SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

tiendeo.jp

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