28.4 sec in total
1.1 sec
26.4 sec
904 ms
Click here to check amazing Pujing 109 content. Otherwise, check out these important facts you probably never knew about pujing109.com
威尼斯人-welcome
Visit pujing109.comWe analyzed Pujing109.com page load time and found that the first response time was 1.1 sec and then it took 27.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% 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.
pujing109.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value8.9 s
1/100
25%
Value14.6 s
1/100
10%
Value890 ms
32/100
30%
Value0
100/100
15%
Value16.8 s
5/100
10%
1134 ms
768 ms
683 ms
743 ms
635 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 6% of them (8 requests) were addressed to the original Pujing109.com, 59% (74 requests) were made to Ofe.chenyz.cn and 17% (21 requests) were made to 590105.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Vc6978.livejoy.net.
Page size can be reduced by 205.5 kB (6%)
3.2 MB
3.0 MB
In fact, the total size of Pujing109.com main page is 3.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 53.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.8 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 53.6 kB or 77% of the original size.
Potential reduce by 2.4 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. Pujing 109 images are well optimized though.
Potential reduce by 79.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 79.5 kB or 67% of the original size.
Potential reduce by 69.9 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. Pujing109.com needs all CSS files to be minified and compressed as it can save up to 69.9 kB or 80% of the original size.
Number of requests can be reduced by 40 (33%)
121
81
The browser has sent 121 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pujing 109. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
pujing109.com
1134 ms
pujing109.com
768 ms
jquery-1.8.2.js
683 ms
jquery-ui.js
743 ms
jquery-ui-1.9.1.custom.min.css
635 ms
me_common.js
680 ms
announment.js
638 ms
ann.css
638 ms
common.js
680 ms
float.js
709 ms
swfobject.js
708 ms
jquery.SuperSlide.2.1.1.js
814 ms
wenan.js
813 ms
netLineCheck.js
814 ms
fp.js
867 ms
collectevent.js
864 ms
refreshBalance.css
864 ms
alertMsg.css
865 ms
reset.css
865 ms
style.css
865 ms
swfobject.js
439 ms
pub.js
873 ms
SuperSlide.2.1.1.js
886 ms
float.js
442 ms
style.css
886 ms
md5.js
886 ms
jquery.forms.js
890 ms
WdatePicker.js
887 ms
gt.js
887 ms
validCode.js
888 ms
style.css
888 ms
monitor.js
19682 ms
colorbox.css
59 ms
jquery.colorbox-min.js
60 ms
login.js
57 ms
jqCookie.js
55 ms
publicReg.js
64 ms
baseValid.js
53 ms
privateReg.js
54 ms
flex
336 ms
82012bb9-19e5-4db2-93e7-cb37d0565afe.gif
51 ms
9e2c322e-43cc-4b59-b827-a8089a8ca8a3.gif
51 ms
f20290ea-2919-4c74-9b31-356eeeb2232f.png
59 ms
665be052-55fb-4752-ba27-ecd97f2c4a6d.png
54 ms
401c2d1f-1e34-478f-9c67-d700a3a305f0.gif
54 ms
87c001f9-5e13-4eaf-bbcd-9749c2d85c1b.png
52 ms
9bdd1447-3c40-4d0b-baa1-d724f983a513.jpg
97 ms
3905fb08-66af-440d-a2f7-aa5e21f14b27.gif
100 ms
79fa7a64-ff6c-49b7-90aa-6182d293d90c.png
101 ms
pop1.png
202 ms
logo.png
149 ms
gq.png
105 ms
01.jpg
145 ms
02.jpg
149 ms
03.jpg
194 ms
04.jpg
153 ms
indexfooterimg.png
194 ms
WdatePicker.css
177 ms
member
405 ms
headerbg.png
249 ms
free.png
342 ms
nav_home_hover.png
339 ms
hot.gif
337 ms
nav_service.png
333 ms
394558de-87bc-4fd0-80f9-178a3147569e.jpg
412 ms
db3eda2b-bb6b-43be-8c3b-63b756c66e3e.png
342 ms
4b87fcfd-600e-46fe-9e3f-fcfe7ab1204d.jpg
343 ms
e513b8a8-dbd9-439a-b775-76bfd2b7aaba.png
409 ms
d70876d1-5297-47c0-b585-82d7087ce8d6.jpg
344 ms
8ff7e77d-30dd-4750-9557-6a992ac8abd8.png
329 ms
646bb51f-2607-446f-8c62-2154d32c4f64.jpg
340 ms
1d1d5da6-6c83-4312-97d3-8cf0b7eb3e90.jpg
342 ms
c1754485-03b5-47fd-8d35-b9451e71bb20.jpg
341 ms
testSpeed
1397 ms
testSpeed
1392 ms
testSpeed
1286 ms
testSpeed
1375 ms
testSpeed
1469 ms
testSpeed
1342 ms
testSpeed
1147 ms
testSpeed
1429 ms
testSpeed
1458 ms
testSpeed
1286 ms
testSpeed
1283 ms
testSpeed
1296 ms
testSpeed
1449 ms
testSpeed
1372 ms
testSpeed
1362 ms
testSpeed
1681 ms
testSpeed
1413 ms
testSpeed
1725 ms
testSpeed
1402 ms
testSpeed
1567 ms
testSpeed
1579 ms
gonggaobg.png
72 ms
itemico.png
76 ms
bottomfg.png
75 ms
bottomico.png
77 ms
GlobalAnnounceServlet
1916 ms
ui-bg_highlight-hard_100_f5f3e5_1x100.png
145 ms
index-pop.html
1352 ms
member
1329 ms
ui-icons_847e71_256x240.png
1021 ms
ui-bg_inset-soft_15_2b2922_1x100.png
1021 ms
overlay.png
1022 ms
index-pop.css
287 ms
jquery-1.8.3.min.js
953 ms
main.js
667 ms
scroll.js
666 ms
pop-scroll.js
1155 ms
hbg.png
229 ms
logo.png
447 ms
icon.png
448 ms
tanchuang_Jc.jpg
446 ms
1.png
225 ms
2.png
437 ms
3.png
446 ms
03.jpg
1747 ms
04.jpg
1321 ms
02.jpg
1120 ms
fimg.png
889 ms
newbg.png
567 ms
lbgcur.png
754 ms
lbg.png
765 ms
rbg.jpg
971 ms
pujing109.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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pujing109.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pujing109.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pujing109.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 Pujing109.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.
pujing109.com
Open Graph description is not detected on the main page of Pujing 109. 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: