24.8 sec in total
1.5 sec
23 sec
253 ms
Visit phoenix-sx.com now to see the best up-to-date Phoenix Sx content and also check out these interesting facts you probably never knew about phoenix-sx.com
山西凤凰胶带有限公司欢迎您的光临!
Visit phoenix-sx.comWe analyzed Phoenix-sx.com page load time and found that the first response time was 1.5 sec and then it took 23.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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
phoenix-sx.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value5.2 s
23/100
25%
Value15.4 s
1/100
10%
Value120 ms
97/100
30%
Value0.698
7/100
15%
Value9.1 s
33/100
10%
1494 ms
1392 ms
1015 ms
1013 ms
1369 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that all of those requests were addressed to Phoenix-sx.com and no external sources were called. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Phoenix-sx.com.
Page size can be reduced by 1.1 MB (19%)
6.1 MB
5.0 MB
In fact, the total size of Phoenix-sx.com main page is 6.1 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. 35% of websites need less resources to load. Images take 5.5 MB which makes up the majority of the site volume.
Potential reduce by 57.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. This page needs HTML code to be minified as it can gain 11.1 kB, which is 17% 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 57.6 kB or 88% of the original size.
Potential reduce by 665.2 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, Phoenix Sx needs image optimization as it can save up to 665.2 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 220.5 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 220.5 kB or 72% of the original size.
Potential reduce by 187.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. Phoenix-sx.com needs all CSS files to be minified and compressed as it can save up to 187.1 kB or 88% of the original size.
Number of requests can be reduced by 13 (22%)
59
46
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phoenix Sx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
phoenix-sx.com
1494 ms
style.css
1392 ms
reset-mob.css
1015 ms
swiper.min.css
1013 ms
animate.min.css
1369 ms
jquery-1.8.0.min.js
1614 ms
animation_define.css
731 ms
slick.css
972 ms
common.js
1258 ms
swiper.min.js
1314 ms
slick.min.js
1101 ms
jquery.placeholder.min.js
1020 ms
jquery.countup.min.js
1151 ms
jquery.waypoints.min.js
1150 ms
public.js
1261 ms
wow.js
1370 ms
body_back.jpg
345 ms
logo.png
279 ms
logo_name.png
272 ms
search_icon.png
358 ms
banner_home01.jpg
2603 ms
banner_home_mobile01-14220528536.jpg
1136 ms
logo1.jpg
5259 ms
logo1-mobile.jpg
4376 ms
085.jpg
2985 ms
085-mobile.jpg
4416 ms
logo3.jpg
11376 ms
logo3-mobile.jpg
6837 ms
logo4.jpg
4171 ms
logo4-mobile.jpg
4765 ms
more_btn.png
4985 ms
20%E9%A1%B5%E5%8E%9F%E5%9B%BE-09580571438.JPG
7030 ms
sanjiao.jpg
5131 ms
23%E9%A1%B5%E5%8E%9F%E5%9B%BE-09594140545.JPG
14921 ms
%E7%AC%AC11%E9%A1%B5%E5%8E%9F%E5%9B%BE-10122115920.jpg
6687 ms
%E8%83%8C%E6%99%AF%E5%9B%BE%E7%89%87-10013080523.JPG
20366 ms
%E8%B6%8A%E5%8D%97%E9%A1%B9%E7%9B%AE24%E9%A1%B5%E5%8E%9F%E5%9B%BE-10025335747.jpg
8670 ms
18%E9%A1%B5%E5%8E%9F%E5%9B%BE-10032692786.JPG
19367 ms
DSC02740%E5%89%AF%E6%9C%AC-10051850761.jpg
12653 ms
%E7%85%A7%E7%89%87252-10154938088.jpg
9889 ms
%E8%83%B6%E6%B5%86%E3%80%81%E8%83%B6%E6%96%99-10182574057.JPG
10845 ms
01.png
11558 ms
02.png
11805 ms
03.png
12092 ms
04.png
12383 ms
05.png
12643 ms
06.png
12843 ms
%E7%AC%AC%E4%B8%80%E7%95%8C%E5%B1%95%E9%94%80%E5%91%A8-10404749088.png
14731 ms
%E8%B6%85%E9%95%BF%E7%AE%A1%E5%B8%A6-10283268320.png
15221 ms
new2.jpg
14457 ms
licheng.jpeg
14975 ms
IMG_2361-1s.jpg
15689 ms
wechat.png
14901 ms
language_icon.png
15142 ms
xiala.png
15079 ms
home_pro_back.jpg
15182 ms
left01.png
14530 ms
right01.png
13060 ms
service_back01.jpg
12868 ms
yinying.png
11774 ms
service_back02.jpg
13108 ms
service_back03.jpg
11764 ms
arrow-left.png
11452 ms
arrow-right.png
11227 ms
bottm_back.jpg
11311 ms
bg-top-top.png
11234 ms
phoenix-sx.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<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
Image elements do not have [alt] attributes
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
phoenix-sx.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
phoenix-sx.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phoenix-sx.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Phoenix-sx.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.
phoenix-sx.com
Open Graph description is not detected on the main page of Phoenix Sx. 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: