Tools & Wizards About Us
fzzr.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

fzzr.com

福州眼镜团购批发--福州中榕钟表眼镜有限公司

Page Load Speed

12.3 sec in total

First Response

2.2 sec

Resources Loaded

9.9 sec

Page Rendered

154 ms

fzzr.com screenshot

About Website

Visit fzzr.com now to see the best up-to-date Fzzr content and also check out these interesting facts you probably never knew about fzzr.com

“中榕眼镜”一九九四年九月一日开业以来，本着“为配镜者负责为己任”的服务宗旨，树立“全体员工质量意识”，在中国眼镜行业率先实施“检测眼镜商店内控标准”（高于国家标准）。商店全体员工均获取由国家、省、市有关部门颁发的验光技师、高级验光师、验光师、配镜师上岗证及隐形眼镜培训证书。为了更好地为广大顾客服务，“中榕眼镜”还聘请了省人民医院眼科专家、医师在周六来“中榕眼镜”坐堂，日常，也配备有专业隐形眼镜配...

Visit fzzr.com

Key Findings

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

fzzr.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value480 ms

60/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

fzzr.com

2205 ms

style.css

322 ms

AJAX.JS

581 ms

ShowInfoList.js

581 ms

Seach.js

613 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 57% of them (25 requests) were addressed to the original Fzzr.com, 18% (8 requests) were made to G.alicdn.com and 9% (4 requests) were made to Player.youku.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Player.youku.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 27.6 kB (4%)

Content Size

623.1 kB

After Optimization

595.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 16.9 kB

  • Original 21.2 kB
  • After minification 15.8 kB
  • After compression 4.4 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 5.5 kB, which is 26% 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 16.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 108 B

  • Original 100.8 kB
  • After minification 100.6 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. Fzzr images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 10.1 kB

  • Original 495.8 kB
  • After minification 495.7 kB
  • After compression 485.7 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.

CSS Optimization

-11%

Potential reduce by 593 B

  • Original 5.4 kB
  • After minification 5.4 kB
  • After compression 4.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. Fzzr.com needs all CSS files to be minified and compressed as it can save up to 593 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (56%)

Requests Now

41

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fzzr.com

fzzr.com

2205 ms

style.css

style.css

322 ms

AJAX.JS

AJAX.JS

581 ms

ShowInfoList.js

ShowInfoList.js

581 ms

Seach.js

Seach.js

613 ms

businessLicense.js

businessLicense.js

240 ms

bg.gif

bg.gif

298 ms

top.gif

top.gif

546 ms

index1_07.jpg

index1_07.jpg

1178 ms

8_1_20070815104913937.JPG

8_1_20070815104913937.JPG

559 ms

4_1_20070823044315765.JPG

4_1_20070823044315765.JPG

557 ms

9_1_20070815112207750.JPG

9_1_20070815112207750.JPG

558 ms

20_1_20090708051335984.JPG

20_1_20090708051335984.JPG

573 ms

wshy.gif

wshy.gif

862 ms

pftd.gif

pftd.gif

877 ms

ygtd.gif

ygtd.gif

877 ms

zzb.gif

zzb.gif

879 ms

XNTk0NjY4OTczNg==

XNTk0NjY4OTczNg==

1479 ms

navbg.gif

navbg.gif

632 ms

leftbg.gif

leftbg.gif

917 ms

barbg.gif

barbg.gif

933 ms

point.gif

point.gif

933 ms

icon-11.gif

icon-11.gif

938 ms

index1_10.gif

index1_10.gif

924 ms

bt.gif

bt.gif

1166 ms

index1_23.gif

index1_23.gif

1166 ms

icon.gif

icon.gif

1179 ms

h.js

h.js

481 ms

h.js

h.js

1062 ms

iframeapi

iframeapi

468 ms

hm.gif

hm.gif

299 ms

unifull.min.css

unifull.min.css

385 ms

aplus_o.js

aplus_o.js

355 ms

index.js

index.js

510 ms

youku-player.umd.min.js

youku-player.umd.min.js

4709 ms

333 ms

eg.js

eg.js

1355 ms

yt.gif

yt.gif

290 ms

index.js

index.js

69 ms

index.js

index.js

72 ms

awsc.js

awsc.js

70 ms

baxiaCommon.js

baxiaCommon.js

72 ms

rp

rp

975 ms

et_n.js

et_n.js

148 ms

Accessibility Review

fzzr.com accessibility score

49

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

fzzr.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fzzr.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

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

fzzr.com

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