Tools & Wizards About Us
futina.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

futina.com

广东福田电器有限公司-墙壁开关排行榜-国产开关品牌-墙壁开关批发

Page Load Speed

25.9 sec in total

First Response

2.6 sec

Resources Loaded

23.2 sec

Page Rendered

121 ms

futina.com screenshot

About Website

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

广东福田电器有限公司主营开关插座,墙壁开关,电工开关,开关面板,家装开关,控制开关凭借过硬的品质与良好的信誉,福田产品远销全球60多个国家和地区

Visit futina.com

Key Findings

We analyzed Futina.com page load time and found that the first response time was 2.6 sec and then it took 23.3 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.

Performance Metrics

futina.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

futina.com

2575 ms

common.css

1134 ms

jquery-1.4.2.min.js

6028 ms

jquery.anyscroll.js

2317 ms

common.js

876 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 83% of them (35 requests) were addressed to the original Futina.com, 7% (3 requests) were made to Tjs.sjs.sinajs.cn and 5% (2 requests) were made to Img.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (17.3 sec) belongs to the original domain Futina.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.2 kB (68%)

Content Size

111.9 kB

After Optimization

35.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futina.com main page is 111.9 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. 15% of websites need less resources to load. Javascripts take 85.9 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 5.3 kB

  • Original 7.9 kB
  • After minification 6.9 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 985 B, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.3 kB or 66% of the original size.

Image Optimization

-9%

Potential reduce by 631 B

  • Original 6.7 kB
  • After minification 6.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. Futina images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 61.7 kB

  • Original 85.9 kB
  • After minification 61.5 kB
  • After compression 24.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 61.7 kB or 72% of the original size.

CSS Optimization

-75%

Potential reduce by 8.6 kB

  • Original 11.5 kB
  • After minification 10.3 kB
  • After compression 2.8 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. Futina.com needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Futina. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

futina.com

futina.com

2575 ms

common.css

common.css

1134 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

6028 ms

jquery.anyscroll.js

jquery.anyscroll.js

2317 ms

common.js

common.js

876 ms

swfobject.js

swfobject.js

17329 ms

logo.png

logo.png

400 ms

tmall_icon.png

tmall_icon.png

388 ms

sina_icon.png

sina_icon.png

389 ms

search_bt_7_13.gif

search_bt_7_13.gif

374 ms

index_dott_r.gif

index_dott_r.gif

371 ms

sub_nav_right_phone.gif

sub_nav_right_phone.gif

457 ms

nav_1.gif

nav_1.gif

740 ms

nav_2.gif

nav_2.gif

752 ms

nav_3.gif

nav_3.gif

772 ms

nav_4.gif

nav_4.gif

774 ms

nav_5.gif

nav_5.gif

791 ms

nav_6.gif

nav_6.gif

918 ms

nav_7.gif

nav_7.gif

2912 ms

footer_icon_1.gif

footer_icon_1.gif

1121 ms

footer_icon_2.gif

footer_icon_2.gif

2626 ms

footer_icon_3.gif

footer_icon_3.gif

1158 ms

footer_icon_4.gif

footer_icon_4.gif

1185 ms

footer_icon_5.gif

footer_icon_5.gif

1381 ms

footer_icon_6.gif

footer_icon_6.gif

2211 ms

nav_1_active.gif

nav_1_active.gif

3913 ms

nav_2_active.gif

nav_2_active.gif

1579 ms

nav_3_active.gif

nav_3_active.gif

1837 ms

nav_4_active.gif

nav_4_active.gif

2378 ms

nav_5_active.gif

nav_5_active.gif

2750 ms

nav_6_active.gif

nav_6_active.gif

2956 ms

nav_7_active.gif

nav_7_active.gif

4443 ms

followbutton.php

followbutton.php

700 ms

search_bg.png

search_bg.png

2977 ms

sub_nav_bg.gif

sub_nav_bg.gif

3176 ms

nav_bg.gif

nav_bg.gif

3247 ms

followButton.css

followButton.css

26 ms

sso.js

sso.js

1021 ms

followButton.js

followButton.js

724 ms

suda.js

suda.js

1466 ms

bg_flbtn.png

bg_flbtn.png

11 ms

b.gif

b.gif

1861 ms

Accessibility Review

futina.com accessibility score

86

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

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

Links do not have a discernible name

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

futina.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

futina.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 uses legible font sizes

High

Tap targets are not sized appropriately

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 Futina.com 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 Futina.com 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

futina.com

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