Tools & Wizards About Us
thinkledge.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% 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

  • 89

    SEO

    Google-friendlier than
    66% of websites

thinkledge.jp

株式会社シンクレッジ – Thinkledge, Inc. | Mobile First Development

Page Load Speed

1.7 sec in total

First Response

84 ms

Resources Loaded

1.4 sec

Page Rendered

228 ms

thinkledge.jp screenshot

About Website

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

スマートフォンアプリ開発、レスポンシブWeb開発、ワードプレスカスタマイズ、IoTデバイス開発など、モバイルファーストの開発なら株式会社シンクレッジにお任せください。

Visit thinkledge.jp

Key Findings

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

Performance Metrics

thinkledge.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

Network Requests Diagram

thinkledge.jp

84 ms

thinkledge.jp

151 ms

analytics.js

19 ms

ggl-fonts.css

68 ms

bootstrap.min.css

114 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 98% of them (50 requests) were addressed to the original Thinkledge.jp, 2% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (724 ms) belongs to the original domain Thinkledge.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.7 kB (3%)

Content Size

1.9 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Thinkledge.jp main page is 1.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 16.1 kB

  • Original 19.3 kB
  • After minification 12.1 kB
  • After compression 3.3 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 7.2 kB, which is 37% 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 16.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 4 B

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

JavaScript Optimization

-31%

Potential reduce by 40.6 kB

  • Original 131.9 kB
  • After minification 131.9 kB
  • After compression 91.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 40.6 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (52%)

Requests Now

33

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thinkledge.jp

thinkledge.jp

84 ms

thinkledge.jp

thinkledge.jp

151 ms

analytics.js

analytics.js

19 ms

ggl-fonts.css

ggl-fonts.css

68 ms

bootstrap.min.css

bootstrap.min.css

114 ms

font-awesome.min.css

font-awesome.min.css

104 ms

animate.css

animate.css

112 ms

main.css

main.css

133 ms

custom.css

custom.css

164 ms

responsive.css

responsive.css

124 ms

preset4.css

preset4.css

154 ms

quick-style.css

quick-style.css

173 ms

jquery.min.js

jquery.min.js

163 ms

jquery.form.min.js

jquery.form.min.js

188 ms

bootstrap.min.js

bootstrap.min.js

218 ms

jquery.flexslider.js

jquery.flexslider.js

344 ms

jquery.nav.js

jquery.nav.js

231 ms

jquery.isotope.min.js

jquery.isotope.min.js

215 ms

main.js

main.js

393 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

392 ms

projects-custom.js

projects-custom.js

394 ms

logo_w.png

logo_w.png

391 ms

news_1.jpg

news_1.jpg

391 ms

portfolio_1.jpg

portfolio_1.jpg

393 ms

portfolio_2.jpg

portfolio_2.jpg

392 ms

portfolio_3.png

portfolio_3.png

418 ms

portfolio_4.jpg

portfolio_4.jpg

418 ms

portfolio_5.jpg

portfolio_5.jpg

417 ms

portfolio_6.jpg

portfolio_6.jpg

487 ms

pattern.png

pattern.png

243 ms

slider4.png

slider4.png

238 ms

slider1.jpg

slider1.jpg

236 ms

slider2.jpg

slider2.jpg

238 ms

slider3.jpg

slider3.jpg

243 ms

overlay-bg.png

overlay-bg.png

279 ms

Raleway-Medium.ttf

Raleway-Medium.ttf

129 ms

Raleway-Regular.ttf

Raleway-Regular.ttf

70 ms

Raleway-Light.ttf

Raleway-Light.ttf

82 ms

Raleway-ExtraLight.ttf

Raleway-ExtraLight.ttf

91 ms

Raleway-Thin.ttf

Raleway-Thin.ttf

477 ms

Raleway-SemiBold.ttf

Raleway-SemiBold.ttf

236 ms

Raleway-Bold.ttf

Raleway-Bold.ttf

192 ms

Raleway-ExtraBold.ttf

Raleway-ExtraBold.ttf

344 ms

Raleway-Black.ttf

Raleway-Black.ttf

299 ms

Roboto-Thin.ttf

Roboto-Thin.ttf

214 ms

Roboto-Light.ttf

Roboto-Light.ttf

593 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

528 ms

Roboto-Medium.ttf

Roboto-Medium.ttf

621 ms

Roboto-Bold.ttf

Roboto-Bold.ttf

507 ms

Roboto-Black.ttf

Roboto-Black.ttf

724 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

684 ms

Accessibility Review

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

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

SEO Factors

thinkledge.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thinkledge.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Thinkledge.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

thinkledge.jp

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