14.7 sec in total
1.4 sec
13.1 sec
106 ms
Welcome to phpin.net homepage info - get ready to check PHPIN best content for China right away, or after learning these important things about phpin.net
PHPIN.NET是帝国CMS爱好者支持站点,包括帝国CMS插件、帝国CMS模板、帝国CMS教程、帝国CMS二次开发、帝国CMS技巧、帝国CMS函数、帝国CMS文件解释、帝国CMS数据字典、平时累积收集的技巧手记等。PHPIN.NET为帝国CMS爱好者的站长建站提供建站动力,为帝国CMS爱好者分享共享资源。
Visit phpin.netWe analyzed Phpin.net page load time and found that the first response time was 1.4 sec and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
phpin.net performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value6.6 s
8/100
25%
Value10.8 s
7/100
10%
Value1,090 ms
24/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
1410 ms
1507 ms
1191 ms
451 ms
1254 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 76% of them (42 requests) were addressed to the original Phpin.net, 4% (2 requests) were made to Tcss.qq.com and 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Phpin.net.
Page size can be reduced by 253.9 kB (28%)
897.3 kB
643.4 kB
In fact, the total size of Phpin.net main page is 897.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 680.0 kB which makes up the majority of the site volume.
Potential reduce by 26.9 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 26.9 kB or 75% of the original size.
Potential reduce by 97.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, PHPIN needs image optimization as it can save up to 97.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 72.4 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 72.4 kB or 67% of the original size.
Potential reduce by 57.4 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. Phpin.net needs all CSS files to be minified and compressed as it can save up to 57.4 kB or 78% of the original size.
Number of requests can be reduced by 30 (58%)
52
22
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PHPIN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
phpin.net
1410 ms
www.phpin.net
1507 ms
style_1_common.css
1191 ms
style_1_forum_index.css
451 ms
common.js
1254 ms
forum.js
708 ms
logging.js
422 ms
forum_slide.js
426 ms
ping.js
970 ms
discuz_tips.js
2766 ms
logo.png
1949 ms
background.png
281 ms
logo.png
248 ms
collapsed_no.gif
214 ms
forum.gif
213 ms
online_admin.gif
215 ms
online_supermod.gif
214 ms
online_moderator.gif
423 ms
online_member.gif
424 ms
switch_width.png
416 ms
px.png
412 ms
newarow.gif
441 ms
pn.png
472 ms
nv.png
617 ms
qmenu.png
618 ms
nv_a.png
620 ms
search.png
634 ms
pt_item.png
644 ms
chart.png
673 ms
category_lbg.png
819 ms
tb.png
820 ms
loading.gif
817 ms
152034jacza7j0h950nc90.png
1416 ms
172834j92u23uu2f38xdrg.png
918 ms
091958hnrskfnfyvtcctot.jpg
1945 ms
181943naafeifake8f4kbf.png
1135 ms
201445j4cb4zvkika4vg2b.jpg
3084 ms
083136p4h77lo5nm11rhdh.jpg
5377 ms
163843xaupp3l3d37qqcpz.jpg
3396 ms
165621zp9s7zc5sgr9szre.png
3817 ms
192238ftk5thz7bgto8uhg.png
2304 ms
205054kk1ke99k204g2giy.png
3629 ms
dot.gif
3209 ms
titlebg.png
3660 ms
MzA0OTgyMzQ=.js
237 ms
push.js
450 ms
stat.php
2185 ms
h.js
1213 ms
stat.htm
158 ms
core.php
1204 ms
9.gif
4499 ms
pic.gif
758 ms
hm.gif
346 ms
scrolltop.png
396 ms
app.gif
1420 ms
phpin.net 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.
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
Links do not have a discernible name
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.
phpin.net 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
phpin.net SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phpin.net 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 Phpin.net 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.
phpin.net
Open Graph description is not detected on the main page of PHPIN. 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: