26.7 sec in total
779 ms
25.5 sec
395 ms
Welcome to ifenso.net homepage info - get ready to check Ifenso best content for China right away, or after learning these important things about ifenso.net
粉搜网-12-22年记录-历史百度权重7
Visit ifenso.netWe analyzed Ifenso.net page load time and found that the first response time was 779 ms and then it took 25.9 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.
ifenso.net performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value11.9 s
0/100
25%
Value9.7 s
11/100
10%
Value10,510 ms
0/100
30%
Value0.011
100/100
15%
Value16.1 s
6/100
10%
779 ms
1066 ms
567 ms
255 ms
254 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 70% of them (54 requests) were addressed to the original Ifenso.net, 6% (5 requests) were made to Bdimg.share.baidu.com and 4% (3 requests) were made to Img.twcczhu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Ope.tanx.com.
Page size can be reduced by 252.6 kB (19%)
1.3 MB
1.1 MB
In fact, the total size of Ifenso.net main page is 1.3 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. 45% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 48.4 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 48.4 kB or 77% of the original size.
Potential reduce by 75.8 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. Ifenso images are well optimized though.
Potential reduce by 106.6 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 106.6 kB or 65% of the original size.
Potential reduce by 21.7 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. Ifenso.net needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 75% of the original size.
Number of requests can be reduced by 24 (33%)
72
48
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ifenso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
ifenso.net
779 ms
www.ifenso.net
1066 ms
jquery.min.js
567 ms
system.js
255 ms
his.js
254 ms
style.css
399 ms
template.js
336 ms
index-96090.js
154 ms
index-96090-2.js
87 ms
index-96090-3.js
150 ms
index-96090-4.js
69 ms
index-96090-5.js
70 ms
index-piao.js
131 ms
slides.js
177 ms
stat.php
3616 ms
56fcb8f10d2d0.jpg
542 ms
53a1527089e5f.jpg
280 ms
4f4203dcc3e08.jpg
222 ms
4f4208aad34d1.jpg
281 ms
56b39399d0515.jpg
449 ms
54d343ccbc913.jpg
270 ms
5662be01a4fe9.jpg
481 ms
56c29fbeb3c6b.jpg
532 ms
4e25b9ec649b0.jpg
393 ms
55a805049dbfd.jpg
388 ms
566ff8d83f68d.jpg
538 ms
50a38dc202cd1.jpg
531 ms
4f4127636cc6f.jpg
600 ms
5543f76924130.jpg
628 ms
56c29c5e102ed.jpg
637 ms
54eef148ba2c7.jpg
697 ms
569601ffdeb17.jpg
683 ms
566fa36a153f9.jpg
646 ms
5624809a8bdb9.jpg
704 ms
56ab672ff1410.jpg
755 ms
56a22679df415.jpg
736 ms
4e3deef2c7a2e.jpg
737 ms
5182e591860fb.jpg
782 ms
569092b4ec0fa.jpg
945 ms
54fc1dd7830ec.jpg
871 ms
554764456fdc0.jpg
992 ms
5705dc97d0096.jpg
991 ms
56aba371beb9e.jpg
944 ms
569c17402ce62.jpg
898 ms
56a65e463b5f3.jpg
1046 ms
5692d7f781459.jpg
1048 ms
logo.png
1033 ms
main.png
1031 ms
main_x_bg.png
1070 ms
slidesbg.png
1078 ms
loading.gif
1130 ms
view.php
1145 ms
jscode.php
1326 ms
ex
957 ms
er_5234_6562.js
4090 ms
tanxssp.js
760 ms
stat.php
4027 ms
ex
20455 ms
9487 ms
rich03.js
1162 ms
shell_v2.js
642 ms
56ab6c9232cfe.jpg
410 ms
566a62180a22a.jpg
600 ms
5633abfa7e62d.jpg
552 ms
556db43253e19.jpg
503 ms
stat.htm
262 ms
core.php
901 ms
bds_s_v2.js
1015 ms
blank
0 ms
9.gif
3990 ms
pic.gif
988 ms
logger.js
767 ms
bdsstyle.css
1557 ms
l6.gif
405 ms
dot.gif
92 ms
close.gif
189 ms
app.gif
4863 ms
ifenso.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
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.
ifenso.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
Browser errors were logged to the console
ifenso.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 doesn't use 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 Ifenso.net 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 Ifenso.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.
ifenso.net
Open Graph description is not detected on the main page of Ifenso. 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: