Tools & Wizards About Us
loglog.jp screenshot

Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

loglog.jp

アマゾソ

Page Load Speed

3.2 sec in total

First Response

973 ms

Resources Loaded

2.1 sec

Page Rendered

132 ms

loglog.jp screenshot

About Website

Click here to check amazing Loglog content for Japan. Otherwise, check out these important facts you probably never knew about loglog.jp

Visit loglog.jp

Key Findings

We analyzed Loglog.jp page load time and found that the first response time was 973 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

loglog.jp performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value2.3 s

99/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

loglog.jp

973 ms

style.css

327 ms

ama.gif

382 ms

icon-books.gif

382 ms

icon-music.gif

383 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 38% of them (21 requests) were addressed to the original Loglog.jp, 49% (27 requests) were made to Ecx.images-amazon.com and 9% (5 requests) were made to Images-jp.amazon.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Loglog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.0 kB (21%)

Content Size

90.4 kB

After Optimization

71.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Loglog.jp main page is 90.4 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. 15% of websites need less resources to load. Images take 49.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.5 kB

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 4.7 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 18.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 49.4 kB
  • After minification 49.4 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. Loglog images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

CSS Optimization

-61%

Potential reduce by 413 B

  • Original 677 B
  • After minification 532 B
  • After compression 264 B

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. Loglog.jp needs all CSS files to be minified and compressed as it can save up to 413 B or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (43%)

Requests Now

54

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

loglog.jp

loglog.jp

973 ms

style.css

style.css

327 ms

ama.gif

ama.gif

382 ms

icon-books.gif

icon-books.gif

382 ms

icon-music.gif

icon-music.gif

383 ms

icon-dvd.gif

icon-dvd.gif

382 ms

icon-ce.gif

icon-ce.gif

510 ms

icon-office_product.gif

icon-office_product.gif

652 ms

icon-kitchen.gif

icon-kitchen.gif

668 ms

icon-toys.gif

icon-toys.gif

667 ms

51J9epZNVdL._SL75_.jpg

51J9epZNVdL._SL75_.jpg

37 ms

stars-4-5.gif

stars-4-5.gif

60 ms

icon-videogames.gif

icon-videogames.gif

688 ms

icon-software.gif

icon-software.gif

715 ms

sports-storeicon.gif

sports-storeicon.gif

833 ms

icon-health_and_beauty.gif

icon-health_and_beauty.gif

980 ms

icon-watch.gif

icon-watch.gif

993 ms

icon-jewelry.gif

icon-jewelry.gif

1017 ms

icon-apparel.gif

icon-apparel.gif

1040 ms

icon-beauty.gif

icon-beauty.gif

1039 ms

icon-baby.gif

icon-baby.gif

1167 ms

icon-grocery.gif

icon-grocery.gif

1321 ms

make-link.gif

make-link.gif

1320 ms

51zgPfzI80L._SL75_.jpg

51zgPfzI80L._SL75_.jpg

241 ms

41izUlMhlcL._SL75_.jpg

41izUlMhlcL._SL75_.jpg

48 ms

51w3kebcQ5L._SL75_.jpg

51w3kebcQ5L._SL75_.jpg

7 ms

51fexTqgSKL._SL75_.jpg

51fexTqgSKL._SL75_.jpg

8 ms

41NIAxz9J-L._SL75_.jpg

41NIAxz9J-L._SL75_.jpg

44 ms

51VMk2uTXsL._SL75_.jpg

51VMk2uTXsL._SL75_.jpg

64 ms

51UsvvEOlFL._SL75_.jpg

51UsvvEOlFL._SL75_.jpg

12 ms

515ms0t2zNL._SL75_.jpg

515ms0t2zNL._SL75_.jpg

63 ms

41aTulEGiBL._SL75_.jpg

41aTulEGiBL._SL75_.jpg

94 ms

41JhaRV6VoL._SL75_.jpg

41JhaRV6VoL._SL75_.jpg

138 ms

51ltpQ93deL._SL75_.jpg

51ltpQ93deL._SL75_.jpg

105 ms

51mGov3aGuL._SL75_.jpg

51mGov3aGuL._SL75_.jpg

70 ms

5155r%2Bv62JL._SL75_.jpg

5155r%2Bv62JL._SL75_.jpg

69 ms

41rD2-OIKfL._SL75_.jpg

41rD2-OIKfL._SL75_.jpg

71 ms

31Kz2UvV3YL._SL75_.jpg

31Kz2UvV3YL._SL75_.jpg

113 ms

music-no-image.gif

music-no-image.gif

54 ms

stars-3-5.gif

stars-3-5.gif

55 ms

51tv%2BRKN8yL._SL75_.jpg

51tv%2BRKN8yL._SL75_.jpg

8 ms

41k4INz1zKL._SL75_.jpg

41k4INz1zKL._SL75_.jpg

100 ms

41fzvI%2BJbVL._SL75_.jpg

41fzvI%2BJbVL._SL75_.jpg

5 ms

41w6w%2BBxP4L._SL75_.jpg

41w6w%2BBxP4L._SL75_.jpg

7 ms

51nAznKfhZL._SL75_.jpg

51nAznKfhZL._SL75_.jpg

128 ms

no-img-sm._V53071204_.gif

no-img-sm._V53071204_.gif

47 ms

51M6rolb3gL._SL75_.jpg

51M6rolb3gL._SL75_.jpg

6 ms

31L-HCuTRvL._SL75_.jpg

31L-HCuTRvL._SL75_.jpg

10 ms

21tmdDw9CWL._SL75_.jpg

21tmdDw9CWL._SL75_.jpg

11 ms

418XivQnZzL._SL75_.jpg

418XivQnZzL._SL75_.jpg

55 ms

41J%2BDinz5HL._SL75_.jpg

41J%2BDinz5HL._SL75_.jpg

15 ms

31-EkNvHQ1L._SL75_.jpg

31-EkNvHQ1L._SL75_.jpg

59 ms

books-no-image.gif

books-no-image.gif

27 ms

ga.js

ga.js

28 ms

__utm.gif

__utm.gif

13 ms

Accessibility Review

loglog.jp accessibility score

48

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

SEO Factors

loglog.jp SEO score

58

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loglog.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Loglog.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

loglog.jp

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