Tools & Wizards About Us
mayoyk.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 36

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 0

    Best Practices

  • 79

    SEO

    Google-friendlier than
    40% of websites

mayoyk.com

www.mayoyk.com-官网首页

Page Load Speed

59.5 sec in total

First Response

4.2 sec

Resources Loaded

54.7 sec

Page Rendered

505 ms

mayoyk.com screenshot

About Website

Visit mayoyk.com now to see the best up-to-date Mayoyk content and also check out these interesting facts you probably never knew about mayoyk.com

长沙美奥口腔官方网站-13-21年记录

Visit mayoyk.com

Key Findings

We analyzed Mayoyk.com page load time and found that the first response time was 4.2 sec and then it took 55.3 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. Unfortunately, there were 40 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

mayoyk.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.1 s

99/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value270 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.145

77/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

index.html

4234 ms

panduan.js

3828 ms

global.css

7619 ms

index.css

1732 ms

addindex.css

1181 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 68% of them (90 requests) were addressed to the original Mayoyk.com, 4% (5 requests) were made to Pft.zoosnet.net and 4% (5 requests) were made to Tjmayo.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Swt.mayoyk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 257.5 kB (60%)

Content Size

427.9 kB

After Optimization

170.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 33.5 kB

  • Original 43.5 kB
  • After minification 39.9 kB
  • After compression 10.0 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 33.5 kB or 77% of the original size.

Image Optimization

-17%

Potential reduce by 14.8 kB

  • Original 84.5 kB
  • After minification 69.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. Obviously, Mayoyk needs image optimization as it can save up to 14.8 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 163.5 kB

  • Original 241.8 kB
  • After minification 225.3 kB
  • After compression 78.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 163.5 kB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 45.7 kB

  • Original 58.2 kB
  • After minification 52.9 kB
  • After compression 12.4 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. Mayoyk.com needs all CSS files to be minified and compressed as it can save up to 45.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (49%)

Requests Now

90

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.html

index.html

4234 ms

panduan.js

panduan.js

3828 ms

global.css

global.css

7619 ms

index.css

index.css

1732 ms

addindex.css

addindex.css

1181 ms

jquerytoolsmin.js

jquerytoolsmin.js

3835 ms

superslide.js

superslide.js

2406 ms

topbanner.js

topbanner.js

2107 ms

Yu-all.js

Yu-all.js

2275 ms

tjswt_new.js

tjswt_new.js

2443 ms

newsyindex.js

newsyindex.js

2470 ms

GlidePic.js

GlidePic.js

2463 ms

stat.php

stat.php

2930 ms

logo.jpg

logo.jpg

3619 ms

zx_qq.gif

zx_qq.gif

4335 ms

bjwwh.jpg

bjwwh.jpg

943 ms

newtitmo.jpg

newtitmo.jpg

1087 ms

wwtzj5.jpg

wwtzj5.jpg

19674 ms

wwtzj1.jpg

wwtzj1.jpg

17592 ms

wwtzj2.jpg

wwtzj2.jpg

3977 ms

wwtzj3.jpg

wwtzj3.jpg

19671 ms

wwtzj4.jpg

wwtzj4.jpg

8296 ms

newpicon11.jpg

newpicon11.jpg

19670 ms

newpicon2.jpg

newpicon2.jpg

12519 ms

newpicon3.jpg

newpicon3.jpg

19670 ms

piconx1.jpg

piconx1.jpg

19670 ms

piconx2.jpg

piconx2.jpg

19671 ms

piconx3.jpg

piconx3.jpg

19672 ms

piconx4.jpg

piconx4.jpg

19673 ms

midads.jpg

midads.jpg

19676 ms

yspic01.jpg

yspic01.jpg

19681 ms

yspic03.jpg

yspic03.jpg

19681 ms

yspic02.jpg

yspic02.jpg

19681 ms

yspic04.jpg

yspic04.jpg

19683 ms

yspic05.jpg

yspic05.jpg

19693 ms

newhd01.jpg

newhd01.jpg

19693 ms

mayoslx1.jpg

mayoslx1.jpg

19696 ms

mayoslx2.jpg

mayoslx2.jpg

19696 ms

symayoslx3.jpg

symayoslx3.jpg

19705 ms

mayoslx4.jpg

mayoslx4.jpg

19708 ms

newhd02.jpg

newhd02.jpg

19743 ms

mayoslx5.jpg

mayoslx5.jpg

19752 ms

mayoslx6.jpg

mayoslx6.jpg

19753 ms

sylsjg01.jpg

sylsjg01.jpg

19753 ms

sylsjg02.jpg

sylsjg02.jpg

19752 ms

sylsjg03.jpg

sylsjg03.jpg

19752 ms

sylsjg04.jpg

sylsjg04.jpg

19752 ms

sylsjg05.jpg

sylsjg05.jpg

19752 ms

sylsjg06.jpg

sylsjg06.jpg

19752 ms

newfotlogo.jpg

newfotlogo.jpg

19752 ms

tel.jpg

tel.jpg

1186 ms

tabqh1.jpg

tabqh1.jpg

7640 ms

tabqh2.jpg

tabqh2.jpg

11277 ms

tabqh3.jpg

tabqh3.jpg

5178 ms

tabqh4.jpg

tabqh4.jpg

2828 ms

slider-arrow.png

slider-arrow.png

3335 ms

360cs1440x385.jpg

360cs1440x385.jpg

19678 ms

sub.jpg

sub.jpg

19652 ms

LsJS.aspx

LsJS.aspx

1946 ms

Yu-swtdiy.js

Yu-swtdiy.js

4147 ms

leftpanel.js

leftpanel.js

4497 ms

sub_1.gif

sub_1.gif

19764 ms

sub_2.gif

sub_2.gif

19618 ms

JS5.aspx

JS5.aspx

3019 ms

sub_3.gif

sub_3.gif

17978 ms

JS_Float.aspx

JS_Float.aspx

931 ms

calendar.js

calendar.js

3462 ms

hm.js

hm.js

2217 ms

2.gif

2.gif

6867 ms

newsid0.aspx

newsid0.aspx

2750 ms

hm.gif

hm.gif

345 ms

327praise1600x385.jpg

327praise1600x385.jpg

19991 ms

sub_5.gif

sub_5.gif

13779 ms

leftpannel0824.png

leftpannel0824.png

17233 ms

closelftc.png

closelftc.png

1368 ms

newswtright.gif

newswtright.gif

19920 ms

7.gif

7.gif

1368 ms

swtstyle.css

swtstyle.css

1467 ms

swtwx03.jpg

swtwx03.jpg

4507 ms

indbtn115115.jpg

indbtn115115.jpg

3728 ms

bottom_tel.png

bottom_tel.png

1566 ms

h.js

h.js

5547 ms

bottom_line.png

bottom_line.png

3202 ms

bottom_time_ico.jpg

bottom_time_ico.jpg

1829 ms

bottom_right.png

bottom_right.png

2228 ms

sub_4.gif

sub_4.gif

9553 ms

21.gif

21.gif

1595 ms

lxb.js

lxb.js

18538 ms

rt.js

rt.js

5002 ms

sa.js

sa.js

5288 ms

hm.gif

hm.gif

987 ms

385zzal1126.jpg

385zzal1126.jpg

20062 ms

newtit01.jpg

newtit01.jpg

20041 ms

i_index_icon02.png

i_index_icon02.png

5381 ms

infowysina.jpg

infowysina.jpg

3269 ms

newtit02.jpg

newtit02.jpg

3281 ms

newmo.jpg

newmo.jpg

3550 ms

tabbj.jpg

tabbj.jpg

4060 ms

tab.jpg

tab.jpg

4387 ms

mayoys.jpg

mayoys.jpg

4431 ms

xq01.jpg

xq01.jpg

4926 ms

zx01.jpg

zx01.jpg

5467 ms

ld01.jpg

ld01.jpg

5494 ms

ld02.jpg

ld02.jpg

5598 ms

ld03.jpg

ld03.jpg

6001 ms

ld04.jpg

ld04.jpg

6426 ms

ld05.jpg

ld05.jpg

6568 ms

ld06.jpg

ld06.jpg

6588 ms

ld07.jpg

ld07.jpg

7534 ms

ld08.jpg

ld08.jpg

7652 ms

newewm.jpg

newewm.jpg

7759 ms

laster.jpg

laster.jpg

19905 ms

wandazj.jpg

wandazj.jpg

19897 ms

yibaobaoxiao.jpg

yibaobaoxiao.jpg

16704 ms

all-on-4.jpg

all-on-4.jpg

19889 ms

lyb.js

lyb.js

7233 ms

stat.htm

stat.htm

211 ms

core.php

core.php

1786 ms

9.gif

9.gif

1048 ms

mvl.js

mvl.js

1556 ms

app.gif

app.gif

1161 ms

mba.js

mba.js

256 ms

mv.js

mv.js

989 ms

t

t

4961 ms

b

b

1048 ms

t

t

983 ms

ckmap.htm

ckmap.htm

1857 ms

log.gif

log.gif

313 ms

_l.js

_l.js

657 ms

log.gif

log.gif

3840 ms

m

m

1932 ms

m

m

1920 ms

m

m

506 ms

Accessibility Review

mayoyk.com accessibility score

36

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

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

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

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

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.

SEO Factors

mayoyk.com SEO score

79

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mayoyk.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mayoyk.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

mayoyk.com

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