Access fghrsh.net. FGHRSH 的博客

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value21.8 s

0/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.316

37/100

15%

TTI (Time to Interactive)

Value8.3 s

40/100

10%

fghrsh.net

5208 ms

main.fghrsh.net

6276 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Fghrsh.net, 50% (1 request) were made to Main.fghrsh.net. The less responsive or slowest element that took the longest time to load (6.3 sec) relates to the external source Main.fghrsh.net.

Content Size

588 B

After Optimization

411 B

In fact, the total size of Fghrsh.net main page is 588 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 588 B which makes up the majority of the site volume.

HTML Optimization

-30%

Potential reduce by 177 B

Original 588 B
After minification 588 B
After compression 411 B

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 177 B or 30% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FGHRSH. 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 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.

High

Image elements do not have [alt] attributes

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

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

UTF8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fghrsh.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 Fghrsh.net main page’s claimed encoding is utf8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

fghrsh.net

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