Tools & Wizards About Us
fshanse.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

fshanse.com

123 - FOSHAN HANSE

Page Load Speed

10.1 sec in total

First Response

769 ms

Resources Loaded

8.4 sec

Page Rendered

980 ms

fshanse.com screenshot

About Website

Click here to check amazing Fs HANSE content. Otherwise, check out these important facts you probably never knew about fshanse.com

SPA TUB Classic Series SPA uses Classic Skirt, standard configurations, and there are a lots of models and colors can for you to choose. If you need a higher standard configurations pool, this is a go...

Visit fshanse.com

Key Findings

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

Performance Metrics

fshanse.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value2,250 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

fshanse.com

769 ms

www.fshanse.com

1449 ms

style.min.css

243 ms

style-main-new.min.css

485 ms

elementor-icons.min.css

701 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 57% of them (50 requests) were addressed to the original Fshanse.com, 42% (37 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Fshanse.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.3 kB (5%)

Content Size

4.3 MB

After Optimization

4.1 MB

  • HTML
  • Images

In fact, the total size of Fshanse.com main page is 4.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. 65% of websites need less resources to load. Images take 4.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 129.0 kB

  • Original 149.8 kB
  • After minification 144.1 kB
  • After compression 20.8 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 129.0 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 83.3 kB

  • Original 4.2 MB
  • After minification 4.1 MB

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. Fs HANSE images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 21 (47%)

Requests Now

45

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fshanse.com

fshanse.com

769 ms

www.fshanse.com

www.fshanse.com

1449 ms

style.min.css

style.min.css

243 ms

style-main-new.min.css

style-main-new.min.css

485 ms

elementor-icons.min.css

elementor-icons.min.css

701 ms

frontend-lite.min.css

frontend-lite.min.css

704 ms

swiper.min.css

swiper.min.css

721 ms

post-121501.css

post-121501.css

734 ms

frontend-lite.min.css

frontend-lite.min.css

721 ms

post-121502.css

post-121502.css

725 ms

post-121475.css

post-121475.css

933 ms

wp-featherlight.min.css

wp-featherlight.min.css

935 ms

css

css

39 ms

fontawesome.min.css

fontawesome.min.css

961 ms

solid.min.css

solid.min.css

963 ms

regular.min.css

regular.min.css

964 ms

brands.min.css

brands.min.css

972 ms

jquery.min.js

jquery.min.js

1403 ms

widget-icon-list.min.css

widget-icon-list.min.css

1170 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

1201 ms

animations.min.css

animations.min.css

1199 ms

hooks.min.js

hooks.min.js

1254 ms

i18n.min.js

i18n.min.js

1255 ms

lazyload.min.js

lazyload.min.js

1413 ms

fc265b656396dc677ba5750fc1506121.js

fc265b656396dc677ba5750fc1506121.js

1684 ms

01.jpg

01.jpg

1199 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

25 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

35 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

36 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

37 ms

fa-regular-400.woff

fa-regular-400.woff

481 ms

fa-solid-900.woff

fa-solid-900.woff

958 ms

fa-brands-400.woff

fa-brands-400.woff

607 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

37 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

39 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

39 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

38 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

59 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

59 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

60 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

61 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

61 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

60 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

61 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

61 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

61 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

62 ms

pxiGyp8kv8JHgFVrJJLucHtF.ttf

pxiGyp8kv8JHgFVrJJLucHtF.ttf

63 ms

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

62 ms

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

64 ms

pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf

pxiDyp8kv8JHgFVrJJLmv1pVF9eL.ttf

64 ms

pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf

pxiAyp8kv8JHgFVrJJLmE0tCMPc.ttf

63 ms

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

64 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

64 ms

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

64 ms

pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf

pxiDyp8kv8JHgFVrJJLm81xVF9eL.ttf

65 ms

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l521wRZWMf_.ttf

66 ms

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

u-440qyriQwlOrhSvowK_l5-fCZJ.ttf

66 ms

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52xwNZWMf_.ttf

65 ms

u-4n0qyriQwlOrhSvowK_l52_wFZWMf_.ttf

u-4n0qyriQwlOrhSvowK_l52_wFZWMf_.ttf

37 ms

logo...png

logo...png

235 ms

1.jpg

1.jpg

1166 ms

%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_202303291758231.jpg

%E5%BE%AE%E4%BF%A1%E5%9B%BE%E7%89%87_202303291758231.jpg

748 ms

57.jpg

57.jpg

1521 ms

58.jpg

58.jpg

914 ms

12-1.jpg

12-1.jpg

990 ms

10-1024x576.jpg

10-1024x576.jpg

1280 ms

19.jpg

19.jpg

1383 ms

13-2.jpg

13-2.jpg

1231 ms

IMG_20180723_090505-1024x768.jpg

IMG_20180723_090505-1024x768.jpg

1241 ms

3.jpg

3.jpg

1401 ms

49.jpg

49.jpg

1472 ms

60.jpg

60.jpg

1484 ms

6.jpg

6.jpg

1761 ms

37.jpg

37.jpg

1850 ms

20.jpg

20.jpg

1636 ms

21.jpg

21.jpg

1953 ms

16.jpg

16.jpg

1725 ms

14-1.jpg

14-1.jpg

1762 ms

19.jpg

19.jpg

1868 ms

18.jpg

18.jpg

1965 ms

Image-Testemonials.jpeg

Image-Testemonials.jpeg

2217 ms

Accessibility Review

fshanse.com accessibility score

95

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

fshanse.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fshanse.com SEO score

77

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

High

Page is blocked from indexing

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fshanse.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fshanse.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

fshanse.com

Open Graph data is detected on the main page of Fs HANSE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: