9.8 sec in total
656 ms
8.4 sec
731 ms
Click here to check amazing Wmphp content. Otherwise, check out these important facts you probably never knew about wmphp.com
北京速光网络专注于为企业提供移动互联网解决方案,从事微信小程序、APP、网站H5、公众号按需开发,为客户建立更强大的营销网络,便于策划并执行个性化、协调一致的营销计划,为用户实现盈利。
Visit wmphp.comWe 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.
wmphp.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.0 s
0/100
25%
Value15.7 s
0/100
10%
Value410 ms
67/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
656 ms
897 ms
2248 ms
214 ms
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 size can be reduced by 1.0 MB (36%)
2.8 MB
1.8 MB
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.
Potential reduce by 617.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 617.3 kB or 72% of the original size.
Potential reduce by 217.9 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, 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.
Potential reduce by 25.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. This website has mostly compressed JavaScripts.
Potential reduce by 150.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. 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.
Number of requests can be reduced by 29 (58%)
50
21
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.
{{url}}
{{time}} ms
wmphp.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
wmphp.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
wmphp.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
ZH
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.
{{og_description}}
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: