Access sfex.net. 无法访问此网站

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value1,400 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.216

57/100

15%

TTI (Time to Interactive)

Value26.2 s

0/100

10%

sfex.net

225 ms

caf.js

40 ms

glp

169 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 67% of them (2 requests) were addressed to the original Sfex.net, 33% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (225 ms) belongs to the original domain Sfex.net.

Content Size

64.0 kB

After Optimization

57.0 kB

In fact, the total size of Sfex.net main page is 64.0 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. Only 5% of websites need less resources to load. Javascripts take 61.7 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 1.1 kB

Original 2.3 kB
After minification 2.3 kB
After compression 1.1 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 1.1 kB or 50% of the original size.

JavaScript Optimization

-9%

Potential reduce by 5.9 kB

Original 61.7 kB
After minification 61.7 kB
After compression 55.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. This website has mostly compressed JavaScripts.

Requests Now

After Optimization

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sfex. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sfex.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 Sfex.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

sfex.net

Open Graph description is not detected on the main page of Sfex. 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: