Tools & Wizards About Us
patriciayun.com screenshot

Report Summary

  • 0

    Performance

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

patriciayun.com

Page Load Speed

863 ms in total

First Response

148 ms

Resources Loaded

553 ms

Page Rendered

162 ms

patriciayun.com screenshot

About Website

Welcome to patriciayun.com homepage info - get ready to check Patriciayun best content right away, or after learning these important things about patriciayun.com

Dr Patricia Yun

Visit patriciayun.com

Key Findings

We analyzed Patriciayun.com page load time and found that the first response time was 148 ms and then it took 715 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

patriciayun.com performance score

0

Network Requests Diagram

patriciayun.com

148 ms

webapp_4D4D4D_a1a1c6.css

66 ms

url.js

166 ms

swfobject.js

104 ms

sitetree.js

155 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Patriciayun.com, 17% (6 requests) were made to Cgi-wsc.chi.us.siteprotect.com. The less responsive or slowest element that took the longest time to load (215 ms) belongs to the original domain Patriciayun.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.8 kB (79%)

Content Size

71.7 kB

After Optimization

14.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Patriciayun.com main page is 71.7 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. 15% of websites need less resources to load. Javascripts take 59.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 8.8 kB

  • Original 12.3 kB
  • After minification 12.1 kB
  • After compression 3.6 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 8.8 kB or 71% of the original size.

JavaScript Optimization

-81%

Potential reduce by 47.8 kB

  • Original 59.1 kB
  • After minification 41.2 kB
  • After compression 11.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 47.8 kB or 81% of the original size.

CSS Optimization

-70%

Potential reduce by 203 B

  • Original 289 B
  • After minification 178 B
  • After compression 86 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. Patriciayun.com needs all CSS files to be minified and compressed as it can save up to 203 B or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (47%)

Requests Now

32

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

patriciayun.com

patriciayun.com

148 ms

webapp_4D4D4D_a1a1c6.css

webapp_4D4D4D_a1a1c6.css

66 ms

url.js

url.js

166 ms

swfobject.js

swfobject.js

104 ms

sitetree.js

sitetree.js

155 ms

table.css

table.css

98 ms

user.css

user.css

144 ms

counter.PicCount

counter.PicCount

113 ms

20150330-231450

20150330-231450

95 ms

oben1.gif

oben1.gif

46 ms

oben2.gif

oben2.gif

81 ms

animation.gif

animation.gif

53 ms

oben3.gif

oben3.gif

61 ms

oben4.gif

oben4.gif

46 ms

logo.gif

logo.gif

45 ms

rechts2.gif

rechts2.gif

79 ms

company_name.gif

company_name.gif

133 ms

links2.gif

links2.gif

85 ms

oben5.gif

oben5.gif

89 ms

menue_bg.gif

menue_bg.gif

147 ms

menue_anfang.gif

menue_anfang.gif

120 ms

2101_h.gif

2101_h.gif

120 ms

2152_n.gif

2152_n.gif

138 ms

2173_n.gif

2173_n.gif

131 ms

2215_n.gif

2215_n.gif

192 ms

2236_n.gif

2236_n.gif

184 ms

menue_ende.gif

menue_ende.gif

171 ms

cont_bg.gif

cont_bg.gif

215 ms

oben6.gif

oben6.gif

184 ms

2101_2105.gif

2101_2105.gif

202 ms

totop.gif

totop.gif

214 ms

date.js

date.js

55 ms

Footer

Footer

53 ms

global_footer.js

global_footer.js

31 ms

wl_footer.js

wl_footer.js

30 ms

Accessibility Review

patriciayun.com accessibility score

53

Accessibility Issues

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

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

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

SEO Factors

patriciayun.com SEO score

83

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

Document doesn't have a <title> element

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Patriciayun.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Patriciayun.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

patriciayun.com

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