Tools & Wizards About Us
sdlab.naist.jp screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

sdlab.naist.jp

SDLab at NAIST

Page Load Speed

3.4 sec in total

First Response

1.2 sec

Resources Loaded

2 sec

Page Rendered

172 ms

sdlab.naist.jp screenshot

About Website

Click here to check amazing SDLab NAIST content for Japan. Otherwise, check out these important facts you probably never knew about sdlab.naist.jp

Visit sdlab.naist.jp

Key Findings

We analyzed Sdlab.naist.jp page load time and found that the first response time was 1.2 sec and then it took 2.2 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

sdlab.naist.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.4 s

71/100

10%

Network Requests Diagram

sdlab.naist.jp

1235 ms

html.css

341 ms

top_new.gif

501 ms

ikari.gif

377 ms

iwesep2014.jpg

512 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that all of those requests were addressed to Sdlab.naist.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Sdlab.naist.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.0 kB (26%)

Content Size

38.1 kB

After Optimization

28.1 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Sdlab.naist.jp main page is 38.1 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. Only 5% of websites need less resources to load. Images take 28.7 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 3.3 kB

  • Original 5.6 kB
  • After minification 5.2 kB
  • After compression 2.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. 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 3.3 kB or 59% of the original size.

Image Optimization

-13%

Potential reduce by 3.7 kB

  • Original 28.7 kB
  • After minification 24.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. Obviously, SDLab NAIST needs image optimization as it can save up to 3.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-77%

Potential reduce by 3.0 kB

  • Original 3.8 kB
  • After minification 2.8 kB
  • After compression 892 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. Sdlab.naist.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 77% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

  • Images
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SDLab NAIST. According to our analytics all requests are already optimized.

Network Requests Diagram

sdlab.naist.jp

sdlab.naist.jp

1235 ms

html.css

html.css

341 ms

top_new.gif

top_new.gif

501 ms

ikari.gif

ikari.gif

377 ms

iwesep2014.jpg

iwesep2014.jpg

512 ms

email.png

email.png

378 ms

sdlab_fudder.gif

sdlab_fudder.gif

382 ms

top_back.gif

top_back.gif

363 ms

border_80.gif

border_80.gif

349 ms

flag_sd.gif

flag_sd.gif

379 ms

top_back_right.gif

top_back_right.gif

412 ms

Accessibility Review

sdlab.naist.jp accessibility score

100

Accessibility Issues

Best Practices

sdlab.naist.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

sdlab.naist.jp SEO score

85

Search Engine Optimization Advices

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 doesn't use 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 Sdlab.naist.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 Sdlab.naist.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

sdlab.naist.jp

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