11.2 sec in total
231 ms
10.8 sec
193 ms
Click here to check amazing 265 content for China. Otherwise, check out these important facts you probably never knew about 265.com
上网导航,网址导航,网站导航,网址之家,网址大全,网址,搜索,音乐,娱乐,图片,小游戏,短信,社区,日记,相册,K歌,通讯簿,BLOG,天气预报,实用工具.最方便,最快捷
Visit 265.comWe analyzed 265.com page load time and found that the first response time was 231 ms and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
265.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value6.5 s
9/100
25%
Value4.6 s
71/100
10%
Value1,900 ms
8/100
30%
Value0.001
100/100
15%
Value9.3 s
31/100
10%
231 ms
1119 ms
217 ms
323 ms
992 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 69% of them (73 requests) were addressed to the original 265.com, 7% (7 requests) were made to Pagead2.googlesyndication.com and 6% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (5.8 sec) relates to the external source Ext.weather.com.cn.
Page size can be reduced by 788.6 kB (43%)
1.8 MB
1.0 MB
In fact, the total size of 265.com main page is 1.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. 55% of websites need less resources to load. Images take 910.9 kB which makes up the majority of the site volume.
Potential reduce by 110.8 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 110.8 kB or 83% of the original size.
Potential reduce by 107.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, 265 needs image optimization as it can save up to 107.9 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 516.9 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 516.9 kB or 71% of the original size.
Potential reduce by 52.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. 265.com needs all CSS files to be minified and compressed as it can save up to 52.9 kB or 82% of the original size.
Number of requests can be reduced by 26 (25%)
103
77
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 265. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
265.com
231 ms
www.265.com
1119 ms
page160218023128-min.css
217 ms
page160218023128-min.js
323 ms
ll.js
992 ms
top_index_half.html
77 ms
top_index.html
80 ms
t1.jpg
1169 ms
h2.jpg
2376 ms
home.gif
101 ms
arrow-down.gif
207 ms
sprite_standard_20120615.gif
214 ms
search-sprite.gif
284 ms
magnifier.png
207 ms
b84fd2fd8e64a8266c32bf9e7f6e536dMTQ1NjcxMjc1Mw.jpg
215 ms
ea3b249fffd09db7781656cbcd5ac9faMTQ1NjcxNjE5OQ.jpg
207 ms
c4dcab3a96dfbf580ec77174b6e00fdbMTQ1NjcxNjIyNQ.jpg
278 ms
f11087de6ca68e5d33227ffefa77f264MTQ1NjM3MTQ1NQ.jpg
277 ms
7153047cc98cc88d1d40c0a37422697aMTQ1NjM3MTQ3Mg.jpg
282 ms
1158bdd1904680a5faf642046fdf5e3aMTQ1NjcxNjMwNg.jpg
289 ms
5b2fd34b4daffe1253b056c718aca9fcMTQ1NjcxNjMyNQ.jpg
414 ms
450b92489ce50fb09e7f265d59c94904MTQ1NjM3MTQxMg.jpg
454 ms
d248c8b38cc92cb70acd011f3fe7d217MTQ1NjM3MTQzMQ.jpg
413 ms
1dcfbd52f99755cba4de75eed97f540aMTQ1NDYzODE3Nw.jpg
415 ms
bd87082d71a0f934eef472bdcf938bddMTQ1NDYzODE5OA.jpg
391 ms
95e12bb9528fb2a6152cba9cd592e6fbMTQ1NDYzODIyMA.jpg
453 ms
405f9dd7cb0c94b1aba1f26819c97a16MTQ1NDYzODI0Nw.jpg
492 ms
f9c04848d5a06cc521db71086bb0c24bMTQ1NDYzODM1MQ.jpg
486 ms
865e998e30c358c941a6c82138557587MTQ1NDYzODM3MA.jpg
487 ms
7129dbb35046521603bac2803cff140dMTQ1NDYzODM5MA.jpg
489 ms
0eb5dd061dc4b7653fc92e66b84b5926MTQ1NDYzODQxMg.jpg
500 ms
cc8db5ac77d5feae07cb8d2cf6dfbd24MTQ1NjcxMTYxNA.jpg
619 ms
9cdf32a29626f44f33301084339bd86fMTQ1NDMwNDQ2NQ.jpg
608 ms
edbd242c059bd5deac1790445c20205dMTQ1NDMwNDkxOA.jpg
723 ms
2c24a4f80ff4715927726c659e24436cMTQ1NDMwNTAwOQ.jpg
616 ms
e976b6d719e3b3956846a724e733009fMTQ1NDMwNTEwMg.jpg
564 ms
118fad61033e12d96f8fb07f773ba895MTQ1NDMwNTEzNQ.jpg
621 ms
72eb60b41f880a3843022531cc132595MTQ1NDMwNTE2NQ.jpg
723 ms
939084c8f6aff8ed7529c241fba793eaMTQ1NDMwNTE4OA.jpg
725 ms
4dcf22249bb17b043c9bb75fb9efef18MTQ1NDMwNTIxMw.jpg
724 ms
e138923e115aba831da7490d06fab819MTQ1NDMwNTM0Nw.jpg
723 ms
f3f103cb4408f7a4d9bd29ad13b0e3e7MTQ1NDMwNTU5Ng.jpg
724 ms
3e04554dd34abcf1e9987358728d3e68MTQ1NDMwNTY3OQ.jpg
815 ms
show_ads.js
5 ms
5bee3bb53b79dab97e02a46121be99d3MTQ1NDMwNTcwNA.jpg
699 ms
12f1650530ee9c15297f4cc21c960b88MTQ1NDMwNTcyNg.jpg
818 ms
ca-pub-7493182811837866.js
34 ms
zrt_lookup.html
32 ms
show_ads_impl.js
51 ms
77e78edb144138abe60cc4b3a6c1e566MTQ1NDMwNTc1Nw.jpg
728 ms
ads
147 ms
osd.js
11 ms
ads
152 ms
af64621c96ca3da1b8f1651fb916ec43MTQ1NDMwNTc4Mg.jpg
623 ms
6db77bf62d9c9b9af0a90f6d4808125eMTQ1NDMwNTgwNQ.jpg
611 ms
7f6174c1e036579c1219548f4a1da71eMTQ1NDMwNTQwMw.jpg
700 ms
29058687b038c3f2dd279da5f96826cfMTQ1NDMwNjA3NA.jpg
790 ms
f37b1a8a1bbef6fecf92b239dbee0562MTQ1NDMwNjEwMQ.jpg
752 ms
8f26ab1c37bdcf2d97ed0c8239de7e50MTQ1NDMwNjEzMA.jpg
632 ms
dd85ec4ce9de96d607a9a2b589d1d872MTQ1NDMwNjE0OQ.jpg
633 ms
7a1a7658b35e23a0692bc88c60c91ef4MTQ1NDMwNjE3Mw.jpg
750 ms
a92456fc5b399a49c0bffb3329473778MTQ1NDMwNjE5Ng.jpg
695 ms
25a35e48ef5ed1256320c96ccad9128eMTQ1NDMwNjIxOA.jpg
745 ms
m_js_controller.js
24 ms
abg.js
41 ms
googlelogo_color_112x36dp.png
31 ms
nessie_icon_magazine_black.png
27 ms
nessie_icon_magazine_white.png
28 ms
s
20 ms
x_button_blue2.png
17 ms
36203615669c62c6b59275e7295bb2ceMTQ1NDMwNTQyMQ.jpg
642 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
8 ms
3f597437dadb6dc914314789fb284f30MTQ1NDMwNjQ5MQ.jpg
762 ms
baa5f6679c03344f19824930bbe909b2MTQ1NDMwNjU3NA.jpg
690 ms
bf31dc6dd1f0507879c8ffe3a52f4068MTQ1NDMwNjU5Nw.jpg
628 ms
57da1859e886c3d857fe1a8af6b00091MTQ1NDMwNjYyMw.jpg
717 ms
b3ea1cf18f6d95d5f4efdf9170805894MTQ1NDMwNjY0NA.jpg
654 ms
28a8cb262baeffa144d457cee2f1d3a3MTQ1NDMwNjY2NA.jpg
626 ms
a6e24a935ca6e6243450b7bf734e0a5eMTQ1NDMwNDg4OQ.jpg
719 ms
56ad32df13bdd4e906f0a3f424496087MTQ1NDMwNDkwMA.jpg
693 ms
82e9a47fefce0fd56a5d58087c17c1efMTQ1NDMwNDkyMw.jpg
746 ms
10077bf6505d6984eba279d092509f1cMTQ1NDMwNDk4NA.jpg
748 ms
ae86bbc0fa22b0a7601b3cb1736d8fecMTQ1NDQwMjI5MA.jpg
682 ms
29f38797ed618ec5aad0cc0cc2cfe999MTQ1NDQwMjMwNQ.jpg
766 ms
b2e839501665e5cdf493facf234f0171MTQ1NDMwNTA2OQ.jpg
693 ms
2d353973cea67836dd2257b9d2c54fbcMTQ1NDMwNTEzNg.jpg
667 ms
41e66e70dd00e42896eff7842e467332MTQ1NDMwNTE2OQ.jpg
691 ms
embed.js
335 ms
analytics.js
5 ms
left_bottom_index.html
654 ms
c120bc87c96ca797af6f60b8133565beMTQ1NDQwMjMyNw.jpg
599 ms
a31e1274dad7985b5f9e453a644a25d8MTQ0NzY2Mjg1Mg.png
688 ms
ads-sprite.png
674 ms
collect
3 ms
collect
48 ms
collect
3 ms
collect
54 ms
home
661 ms
activeview
13 ms
ads
247 ms
activeview
13 ms
jquery_a4373ccd.js
665 ms
favicon
31 ms
nessie_icon_thin_arrow_big_white.png
14 ms
56451.js
5753 ms
ui
37 ms
265.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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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
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.
265.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
265.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 265.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 265.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.
265.com
Open Graph description is not detected on the main page of 265. 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: