Tools & Wizards About Us
udc.or.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 70

    SEO

    Google-friendlier than
    30% of websites

udc.or.jp

公益財団法人都市づくりパブリックデザインセンター（公式ホームページ）

Page Load Speed

8.7 sec in total

First Response

529 ms

Resources Loaded

7.8 sec

Page Rendered

368 ms

udc.or.jp screenshot

About Website

Welcome to udc.or.jp homepage info - get ready to check Udc best content right away, or after learning these important things about udc.or.jp

公益財団法人都市づくりパブリックデザインセンターのHOMEです

Visit udc.or.jp

Key Findings

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

Performance Metrics

udc.or.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value18.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,330 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.211

59/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

udc.or.jp

529 ms

www.udc.or.jp

1810 ms

reset.css

323 ms

pc.css

635 ms

font-awesome.css

485 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 84% of them (59 requests) were addressed to the original Udc.or.jp, 6% (4 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Udc.or.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Udc.or.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.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 113.2 kB

  • Original 138.5 kB
  • After minification 136.8 kB
  • After compression 25.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 113.2 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 6.6 kB

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

JavaScript Optimization

-8%

Potential reduce by 14.5 kB

  • Original 176.1 kB
  • After minification 176.1 kB
  • After compression 161.6 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

-20%

Potential reduce by 12.2 kB

  • Original 62.3 kB
  • After minification 62.2 kB
  • After compression 50.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. Udc.or.jp needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (61%)

Requests Now

67

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

udc.or.jp

udc.or.jp

529 ms

www.udc.or.jp

www.udc.or.jp

1810 ms

reset.css

reset.css

323 ms

pc.css

pc.css

635 ms

font-awesome.css

font-awesome.css

485 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

487 ms

photoswipe.css

photoswipe.css

517 ms

default-skin.css

default-skin.css

576 ms

froala_editor.pkgd.min.css

froala_editor.pkgd.min.css

625 ms

custom.css

custom.css

647 ms

design.css

design.css

652 ms

page.css

page.css

689 ms

jquery-3.5.1.js

jquery-3.5.1.js

1109 ms

jquery-migrate-1.4.1.js

jquery-migrate-1.4.1.js

860 ms

resize_img.js

resize_img.js

792 ms

jquery.easing.min.js

jquery.easing.min.js

809 ms

jquery.cookie.min.js

jquery.cookie.min.js

812 ms

ua_log.js

ua_log.js

860 ms

msg.js

msg.js

952 ms

camera.css

camera.css

971 ms

pc.css

pc.css

982 ms

js

js

64 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

2319 ms

photoswipe.min.js

photoswipe.min.js

877 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

2318 ms

photoswipe-set-customize.min.js

photoswipe-set-customize.min.js

2319 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

2319 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

2320 ms

camera.js

camera.js

2321 ms

sdk.js

sdk.js

17 ms

marquee.min.js

marquee.min.js

2321 ms

onload.min.js

onload.min.js

2319 ms

scrollmenu.js

scrollmenu.js

2320 ms

analysis.js

analysis.js

2321 ms

fontplus.js

fontplus.js

2318 ms

header_bg.png

header_bg.png

212 ms

201712181717393477.png

201712181717393477.png

213 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

487 ms

catch_bg.png

catch_bg.png

321 ms

bg.png

bg.png

218 ms

h_menu_bg.png

h_menu_bg.png

198 ms

h_menu_left_btn.png

h_menu_left_btn.png

284 ms

sprite.png

sprite.png

334 ms

h_menu_right_btn.png

h_menu_right_btn.png

345 ms

201910261831367666.gif

201910261831367666.gif

653 ms

b_title.png

b_title.png

447 ms

201711171809198705.png

201711171809198705.png

1479 ms

201711171829032874.png

201711171829032874.png

983 ms

201711171830199115.png

201711171830199115.png

1030 ms

201711171831323863.png

201711171831323863.png

1093 ms

201711171832312661.png

201711171832312661.png

961 ms

201711171833127000.png

201711171833127000.png

1402 ms

20191026234745906.gif

20191026234745906.gif

1121 ms

201908071539163339.gif

201908071539163339.gif

1146 ms

201908071539321699.gif

201908071539321699.gif

1202 ms

bottom_bg.jpg

bottom_bg.jpg

1256 ms

footer_bg.png

footer_bg.png

1279 ms

qr.png

qr.png

1308 ms

widgets.js

widgets.js

118 ms

sdk.js

sdk.js

33 ms

camera-loader.gif

camera-loader.gif

1207 ms

20171207104529616.jpg

20171207104529616.jpg

1412 ms

catch_frame.png

catch_frame.png

1273 ms

48 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

49 ms

settings

settings

71 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

18 ms

embeds

embeds

33 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

31 ms

202405221126016555.png

202405221126016555.png

325 ms

Accessibility Review

udc.or.jp accessibility score

84

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

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

Best Practices

udc.or.jp 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

udc.or.jp SEO score

70

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

High

Image elements do not have [alt] attributes

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Udc.or.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 Udc.or.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

udc.or.jp

Open Graph data is detected on the main page of Udc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: