Tools & Wizards About Us
wmphp.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

wmphp.com

完美源码-速光网络旗下源码站

Page Load Speed

9.8 sec in total

First Response

656 ms

Resources Loaded

8.4 sec

Page Rendered

731 ms

wmphp.com screenshot

About Website

Click here to check amazing Wmphp content. Otherwise, check out these important facts you probably never knew about wmphp.com

北京速光网络专注于为企业提供移动互联网解决方案，从事微信小程序、APP、网站H5、公众号按需开发，为客户建立更强大的营销网络，便于策划并执行个性化、协调一致的营销计划，为用户实现盈利。

Visit wmphp.com

Key Findings

We analyzed Wmphp.com page load time and found that the first response time was 656 ms and then it took 9.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

wmphp.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

wmphp.com

656 ms

wmphp.com

897 ms

www.wmphp.com

2248 ms

animate.css

214 ms

app.css

643 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 65% of them (37 requests) were addressed to the original Wmphp.com, 21% (12 requests) were made to Down.wmphp.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Down.wmphp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (36%)

Content Size

2.8 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wmphp.com main page is 2.8 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 617.3 kB

  • Original 855.7 kB
  • After minification 817.5 kB
  • After compression 238.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. 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 617.3 kB or 72% of the original size.

Image Optimization

-17%

Potential reduce by 217.9 kB

  • Original 1.3 MB
  • After minification 1.1 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. Obviously, Wmphp needs image optimization as it can save up to 217.9 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

-6%

Potential reduce by 25.3 kB

  • Original 399.5 kB
  • After minification 399.5 kB
  • After compression 374.2 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

-56%

Potential reduce by 150.1 kB

  • Original 269.8 kB
  • After minification 266.8 kB
  • After compression 119.6 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. Wmphp.com needs all CSS files to be minified and compressed as it can save up to 150.1 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (58%)

Requests Now

50

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wmphp.com

wmphp.com

656 ms

wmphp.com

wmphp.com

897 ms

www.wmphp.com

www.wmphp.com

2248 ms

animate.css

animate.css

214 ms

app.css

app.css

643 ms

diy.css

diy.css

1062 ms

uibanner.css

uibanner.css

640 ms

swiper.min.css

swiper.min.css

640 ms

jhs_alifont.css

jhs_alifont.css

641 ms

light.css

light.css

651 ms

video.css

video.css

851 ms

YD-dark.css

YD-dark.css

851 ms

shortcodes.css

shortcodes.css

1072 ms

external.css

external.css

858 ms

sweetalert2.min.css

sweetalert2.min.css

856 ms

diy.css

diy.css

1069 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

1069 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

1283 ms

prism.js

prism.js

1080 ms

sweetalert2.min.js

sweetalert2.min.js

1272 ms

font_1369336_w5ye2sex6w.js

font_1369336_w5ye2sex6w.js

101 ms

view-history.js

view-history.js

1269 ms

wow.min.js

wow.min.js

1273 ms

gundong.js

gundong.js

1274 ms

activate-power-mode.js

activate-power-mode.js

1414 ms

countUp.js

countUp.js

430 ms

swiper.min.js

swiper.min.js

1482 ms

notice.js

notice.js

1488 ms

app.js

app.js

1491 ms

xb-app.js

xb-app.js

1493 ms

shortcodes.js

shortcodes.js

1494 ms

plugins.js

plugins.js

1497 ms

1607150586-d09ac3b546e87a2.png

1607150586-d09ac3b546e87a2.png

1266 ms

1609072501-6eb57bee3debdfa.jpg

1609072501-6eb57bee3debdfa.jpg

1692 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

492 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

916 ms

hm.js

hm.js

2151 ms

push.js

push.js

1189 ms

wave_05.svg

wave_05.svg

252 ms

wave_04.svg

wave_04.svg

250 ms

1-21120610523DS.png

1-21120610523DS.png

1953 ms

0.0.31.97

0.0.31.97

8 ms

0.0.31.88

0.0.31.88

8 ms

1608467636-c4ca4238a0b9238.png

1608467636-c4ca4238a0b9238.png

2693 ms

1680097154-6512bd43d9caa6e.jpg

1680097154-6512bd43d9caa6e.jpg

2388 ms

img_62b975f61aeb8.png

img_62b975f61aeb8.png

1831 ms

1629120921-c4ca4238a0b9238.png

1629120921-c4ca4238a0b9238.png

2093 ms

1624942437-c4ca4238a0b9238-571x1024.jpeg

1624942437-c4ca4238a0b9238-571x1024.jpeg

2874 ms

1629024125-c4ca4238a0b9238.jpg

1629024125-c4ca4238a0b9238.jpg

2091 ms

img_64381b944d649.png

img_64381b944d649.png

2128 ms

img_64d4bdfbaeb34.png

img_64d4bdfbaeb34.png

543 ms

img_64a84677633e1.png

img_64a84677633e1.png

507 ms

1661689468-20def7942674282.png

1661689468-20def7942674282.png

745 ms

hm.gif

hm.gif

335 ms

timthumb.php

timthumb.php

219 ms

1.png

1.png

215 ms

timthumb.php

timthumb.php

218 ms

Accessibility Review

wmphp.com accessibility score

56

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

Form elements do not have associated labels

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

wmphp.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wmphp.com SEO score

83

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

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

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

wmphp.com

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