Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ifenso.net

www.ifenso.net-官网首页

Page Load Speed

26.7 sec in total

First Response

779 ms

Resources Loaded

25.5 sec

Page Rendered

395 ms

ifenso.net screenshot

About Website

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.net

Key Findings

We 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.

Performance Metrics

ifenso.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value10,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

ifenso.net

779 ms

www.ifenso.net

1066 ms

jquery.min.js

567 ms

system.js

255 ms

his.js

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 Optimization Overview & Recommendations

Page size can be reduced by 252.6 kB (19%)

Content Size

1.3 MB

After Optimization

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.

HTML Optimization

-77%

Potential reduce by 48.4 kB

  • Original 63.1 kB
  • After minification 60.0 kB
  • After compression 14.7 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.

Image Optimization

-7%

Potential reduce by 75.8 kB

  • Original 1.0 MB
  • After minification 974.0 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.

JavaScript Optimization

-65%

Potential reduce by 106.6 kB

  • Original 164.8 kB
  • After minification 160.5 kB
  • After compression 58.2 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.

CSS Optimization

-75%

Potential reduce by 21.7 kB

  • Original 29.0 kB
  • After minification 24.1 kB
  • After compression 7.3 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.

Requests Breakdown

Number of requests can be reduced by 24 (33%)

Requests Now

72

After Optimization

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.

Accessibility Review

ifenso.net accessibility score

76

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ifenso.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ifenso.net SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: