Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

fouka.com

域名售卖

Page Load Speed

6.1 sec in total

First Response

175 ms

Resources Loaded

5.8 sec

Page Rendered

170 ms

fouka.com screenshot

About Website

Welcome to fouka.com homepage info - get ready to check Fouka best content right away, or after learning these important things about fouka.com

Visit fouka.com

Key Findings

We analyzed Fouka.com page load time and found that the first response time was 175 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

fouka.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

fouka.com

175 ms

www.easyknow.com

3274 ms

18753605.js

1231 ms

5201.png

930 ms

icon_3.gif

770 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that 20% of them (1 request) were addressed to the original Fouka.com, 40% (2 requests) were made to Easyknow.com and 20% (1 request) were made to Js.users.51.la. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Easyknow.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 152.0 kB (14%)

Content Size

1.1 MB

After Optimization

901.8 kB

In fact, the total size of Fouka.com main page is 1.1 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-42%

Potential reduce by 558 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 769 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 558 B or 42% of the original size.

Image Optimization

-14%

Potential reduce by 150.3 kB

  • Original 1.1 MB
  • After minification 900.3 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, Fouka needs image optimization as it can save up to 150.3 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 1.2 kB

  • Original 2.0 kB
  • After minification 1.9 kB
  • After compression 766 B

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 1.2 kB or 61% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

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

Accessibility Review

fouka.com accessibility score

68

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

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

fouka.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fouka.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fouka.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fouka.com main page’s claimed encoding is gb2312. 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

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