Tools & Wizards About Us
pfm2019.org screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

pfm2019.org

Asia-Pacific PFM 2019

Page Load Speed

33.9 sec in total

First Response

3.2 sec

Resources Loaded

30.1 sec

Page Rendered

579 ms

pfm2019.org screenshot

About Website

Click here to check amazing PFM 2019 content. Otherwise, check out these important facts you probably never knew about pfm2019.org

2019 Asia-Pacific Workshop on Piezoresponse Force Microscopy and Nanoscale Electromechanics of Functional Materials and Electrochemical Systems (Asia-Pacific PFM 2019)

Visit pfm2019.org

Key Findings

We analyzed Pfm2019.org page load time and found that the first response time was 3.2 sec and then it took 30.7 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.

Performance Metrics

pfm2019.org performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value25.5 s

0/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

pfm2019.org

3165 ms

common.css

397 ms

owl.carousel.css

1338 ms

style.css

3699 ms

jquery-1.12.4.min.js

7939 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 78% of them (54 requests) were addressed to the original Pfm2019.org, 9% (6 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Abs.twimg.com. The less responsive or slowest element that took the longest time to load (18.9 sec) belongs to the original domain Pfm2019.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.5 kB (44%)

Content Size

421.4 kB

After Optimization

233.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pfm2019.org main page is 421.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. 35% of websites need less resources to load. Images take 170.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 39.6 kB

  • Original 44.9 kB
  • After minification 32.2 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 12.7 kB, which is 28% 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 39.6 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 2.8 kB

  • Original 170.4 kB
  • After minification 167.7 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. PFM 2019 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 112.3 kB

  • Original 165.3 kB
  • After minification 162.7 kB
  • After compression 53.0 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 112.3 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 32.8 kB

  • Original 40.8 kB
  • After minification 34.8 kB
  • After compression 7.9 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. Pfm2019.org needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (20%)

Requests Now

64

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PFM 2019. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pfm2019.org

pfm2019.org

3165 ms

common.css

common.css

397 ms

owl.carousel.css

owl.carousel.css

1338 ms

style.css

style.css

3699 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

7939 ms

owl.carousel.min.js

owl.carousel.min.js

3885 ms

select.js

select.js

2449 ms

ui.js

ui.js

1542 ms

bizvalley.js

bizvalley.js

2254 ms

widgets.js

widgets.js

130 ms

jquery.form.min.js

jquery.form.min.js

568 ms

top_i01.png

top_i01.png

233 ms

top_i02.png

top_i02.png

471 ms

logo.png

logo.png

467 ms

main_img03.png

main_img03.png

14257 ms

slide03_tit.png

slide03_tit.png

2010 ms

Asia-Pacific.png

Asia-Pacific.png

1233 ms

PHOTOS01.png

PHOTOS01.png

4171 ms

PHOTOS02.png

PHOTOS02.png

4029 ms

PHOTOS03.png

PHOTOS03.png

2080 ms

PHOTOS04.png

PHOTOS04.png

2833 ms

PHOTOS05.png

PHOTOS05.png

2971 ms

PHOTOS06.png

PHOTOS06.png

4243 ms

PHOTOS07.png

PHOTOS07.png

4476 ms

PHOTOS08.png

PHOTOS08.png

4568 ms

link_i01.png

link_i01.png

4212 ms

link_i02.png

link_i02.png

4361 ms

link_i03.png

link_i03.png

4405 ms

link_i04.png

link_i04.png

4467 ms

link_i05.png

link_i05.png

4561 ms

link_i06.png

link_i06.png

4602 ms

book_btn.png

book_btn.png

4642 ms

check_i01.png

check_i01.png

4634 ms

check_i02.png

check_i02.png

4746 ms

plus_i.png

plus_i.png

4749 ms

ps_img1.png

ps_img1.png

7013 ms

ps_img2.png

ps_img2.png

6186 ms

ps_img3.png

ps_img3.png

5449 ms

square_444.png

square_444.png

4942 ms

n_i.png

n_i.png

4957 ms

Organized_i.png

Organized_i.png

5141 ms

Organized_logo02.png

Organized_logo02.png

5355 ms

Organized_logo01.png

Organized_logo01.png

5332 ms

kaist.jpg

kaist.jpg

7961 ms

BK21.png

BK21.png

8220 ms

skku.jpg

skku.jpg

6010 ms

cau.bmp

cau.bmp

8508 ms

NotoSansKR-Regular-Hestia.woff

NotoSansKR-Regular-Hestia.woff

17423 ms

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

48 ms

NotoSansKR-Medium-Hestia.woff

NotoSansKR-Medium-Hestia.woff

18342 ms

NotoSansKR-Light-Hestia.woff

NotoSansKR-Light-Hestia.woff

18898 ms

settings

settings

168 ms

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

moment~timeline~tweet.ae149926685a43cb146e35371430188e.js

12 ms

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

timeline.687eed636a16648c9f0b1f72d7fa68bd.js

12 ms

profile

profile

154 ms

1f600.png

1f600.png

42 ms

1f642.png

1f642.png

63 ms

1f44d.png

1f44d.png

63 ms

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css

15 ms

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css

timeline.32f7f89e2e680ebfe3f4cfefb27966ae.light.ltr.css

22 ms

LTdilYZZ_normal.jpg

LTdilYZZ_normal.jpg

241 ms

D3Iar_6XcAIz_xI

D3Iar_6XcAIz_xI

657 ms

D3H1-BwUYAALFgL

D3H1-BwUYAALFgL

637 ms

jot

jot

34 ms

NotoSansKR-Bold-Hestia.woff

NotoSansKR-Bold-Hestia.woff

18871 ms

kofst.png

kofst.png

6875 ms

seoul_ci.jpg

seoul_ci.jpg

7613 ms

item_left.png

item_left.png

7068 ms

item_right.png

item_right.png

7119 ms

Accessibility Review

pfm2019.org accessibility score

80

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

pfm2019.org best practices score

75

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

SEO Factors

pfm2019.org SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

pfm2019.org

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