Tools & Wizards About Us
59log.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

59log.com

語句ログ - ニュース、プログラミング、システムトレードの用語解説

Page Load Speed

23.4 sec in total

First Response

562 ms

Resources Loaded

22.4 sec

Page Rendered

444 ms

59log.com screenshot

About Website

Welcome to 59log.com homepage info - get ready to check 59 Log best content for Japan right away, or after learning these important things about 59log.com

日本の注目ニュース、コンピュータープログラミング（C/C++,Perl,PHP,SQL）、システムトレード（FX,CFD,株価指数,先物）に関する語句（Word）を日本語や英語で解説

Visit 59log.com

Key Findings

We analyzed 59log.com page load time and found that the first response time was 562 ms and then it took 22.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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

59log.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

59log.com

562 ms

59log.com

1210 ms

theme.css

178 ms

main_min.js

354 ms

adsbygoogle.js

416 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 10% of them (6 requests) were addressed to the original 59log.com, 24% (14 requests) were made to Googleads.g.doubleclick.net and 15% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Ads.affstrack.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 460.4 kB (40%)

Content Size

1.1 MB

After Optimization

687.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 59log.com 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. 45% of websites need less resources to load. Javascripts take 875.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 110.6 kB

  • Original 134.0 kB
  • After minification 133.1 kB
  • After compression 23.4 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 110.6 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 34 B

  • Original 136.3 kB
  • After minification 136.2 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. 59 Log images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 348.7 kB

  • Original 875.0 kB
  • After minification 875.0 kB
  • After compression 526.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 348.7 kB or 40% of the original size.

CSS Optimization

-34%

Potential reduce by 1.0 kB

  • Original 3.0 kB
  • After minification 3.0 kB
  • After compression 2.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. 59log.com needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (57%)

Requests Now

51

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

59log.com

59log.com

562 ms

59log.com

59log.com

1210 ms

theme.css

theme.css

178 ms

main_min.js

main_min.js

354 ms

adsbygoogle.js

adsbygoogle.js

416 ms

6274

6274

678 ms

RqZd0WyCSxa86Rv

RqZd0WyCSxa86Rv

252 ms

large.jpg

large.jpg

133 ms

127526

127526

20227 ms

tablet.css

tablet.css

180 ms

show_ads_impl.js

show_ads_impl.js

314 ms

ga.js

ga.js

18 ms

__utm.gif

__utm.gif

12 ms

smart.css

smart.css

178 ms

zrt_lookup.html

zrt_lookup.html

36 ms

ads

ads

501 ms

ads

ads

394 ms

ads

ads

195 ms

ads

ads

478 ms

reactive_library.js

reactive_library.js

206 ms

ca-pub-9656762096049149

ca-pub-9656762096049149

121 ms

ads

ads

151 ms

ads

ads

173 ms

ads

ads

395 ms

ads

ads

393 ms

ads

ads

388 ms

ads

ads

387 ms

ads

ads

381 ms

14137971252082864543

14137971252082864543

348 ms

load_preloaded_resource.js

load_preloaded_resource.js

60 ms

abg_lite.js

abg_lite.js

274 ms

window_focus.js

window_focus.js

277 ms

qs_click_protection.js

qs_click_protection.js

93 ms

ufs_web_display.js

ufs_web_display.js

42 ms

e92e9b19fdbae9b3a3ef41360efccaf5.js

e92e9b19fdbae9b3a3ef41360efccaf5.js

313 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

80 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

267 ms

pixel

pixel

302 ms

8324732904621422289

8324732904621422289

332 ms

abg_lite.js

abg_lite.js

44 ms

omrhp.js

omrhp.js

255 ms

Q12zgMmT.js

Q12zgMmT.js

290 ms

icon.png

icon.png

312 ms

gen_204

gen_204

281 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

309 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

311 ms

css

css

140 ms

pixel

pixel

103 ms

pixel

pixel

129 ms

62bHydCX.html

62bHydCX.html

70 ms

activeview

activeview

151 ms

EwGoFmJh85jiKfF-1zVyLpKT-mfRa9zDiFbQBwafAqI.js

EwGoFmJh85jiKfF-1zVyLpKT-mfRa9zDiFbQBwafAqI.js

4 ms

font

font

101 ms

font

font

101 ms

rum

rum

31 ms

bounce

bounce

23 ms

pixel

pixel

18 ms

pixel

pixel

22 ms

rum

rum

27 ms

Accessibility Review

59log.com 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.

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

Form elements do not have associated labels

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

59log.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Page has valid source maps

SEO Factors

59log.com SEO score

87

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 59log.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that 59log.com 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

59log.com

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