Tools & Wizards About Us
twinflag.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

twinflag.com

双旗科技-引领智慧显示新未来

Page Load Speed

27.1 sec in total

First Response

679 ms

Resources Loaded

25.9 sec

Page Rendered

461 ms

twinflag.com screenshot

About Website

Click here to check amazing Twinflag content. Otherwise, check out these important facts you probably never knew about twinflag.com

双旗科技专注于商业显示领域，为机场、地铁、商场等场景提供拼接屏，数字标牌广告机，触摸屏，透明屏，条形屏等多种商显应用。热线400-810-3999。

Visit twinflag.com

Key Findings

We analyzed Twinflag.com page load time and found that the first response time was 679 ms and then it took 26.4 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

twinflag.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value21.9 s

0/100

10%

TBT (Total Blocking Time)

Value590 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.501

16/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

twinflag.com

679 ms

www.twinflag.com.cn

754 ms

www.twinflag.com.cn

1230 ms

bootstrap.min.css

893 ms

font-awesome.min.css

673 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Twinflag.com, 93% (81 requests) were made to Twinflag.com.cn and 2% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Twinflag.com.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 369.7 kB (9%)

Content Size

4.3 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twinflag.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. 50% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 106.0 kB

  • Original 118.8 kB
  • After minification 64.0 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 54.8 kB, which is 46% 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 106.0 kB or 89% of the original size.

Image Optimization

-6%

Potential reduce by 229.9 kB

  • Original 3.8 MB
  • After minification 3.6 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. Twinflag images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 14.7 kB

  • Original 285.2 kB
  • After minification 285.2 kB
  • After compression 270.5 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

-25%

Potential reduce by 19.0 kB

  • Original 77.5 kB
  • After minification 74.0 kB
  • After compression 58.5 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. Twinflag.com needs all CSS files to be minified and compressed as it can save up to 19.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (29%)

Requests Now

84

After Optimization

60

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twinflag.com

twinflag.com

679 ms

www.twinflag.com.cn

www.twinflag.com.cn

754 ms

www.twinflag.com.cn

www.twinflag.com.cn

1230 ms

bootstrap.min.css

bootstrap.min.css

893 ms

font-awesome.min.css

font-awesome.min.css

673 ms

swiper.min.css

swiper.min.css

671 ms

header.css

header.css

675 ms

footer.css

footer.css

675 ms

baseContent.css

baseContent.css

897 ms

animate.min.css

animate.min.css

1345 ms

scroll_top.css

scroll_top.css

1347 ms

layui.css

layui.css

1348 ms

login.css

login.css

1347 ms

base.css

base.css

1558 ms

index2.css

index2.css

1573 ms

swiper.min.js

swiper.min.js

2027 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

2027 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

2047 ms

base.js

base.js

1803 ms

jquery.form.js

jquery.form.js

2014 ms

layer_zh-cn.js

layer_zh-cn.js

2015 ms

layui.js

layui.js

2476 ms

wxLogin.js

wxLogin.js

420 ms

wow.js

wow.js

2683 ms

hm.js

hm.js

944 ms

62a1a85a8aea7.png

62a1a85a8aea7.png

1341 ms

60f7e9fd56ab7.png

60f7e9fd56ab7.png

1348 ms

60f7e9e2c7e8e.png

60f7e9e2c7e8e.png

1350 ms

tel-icon.png

tel-icon.png

1351 ms

logings1.png

logings1.png

1802 ms

sub_search.jpg

sub_search.jpg

2003 ms

login.jpg

login.jpg

2009 ms

62a41bd018aa3.png

62a41bd018aa3.png

9629 ms

bannermore.png

bannermore.png

2246 ms

62a41bd9602cd.png

62a41bd9602cd.png

14413 ms

62a1bfc80b731.png

62a1bfc80b731.png

13838 ms

62a41404af6b6.png

62a41404af6b6.png

12181 ms

62a41339b6e6f.jpg

62a41339b6e6f.jpg

6334 ms

62a1b070d8bb0.png

62a1b070d8bb0.png

16244 ms

1de2444f8d5ff75318cd3176ed0fcd55.jpg

1de2444f8d5ff75318cd3176ed0fcd55.jpg

8579 ms

14dfc7a2c7da9801c34a20bf849f4e6a.png

14dfc7a2c7da9801c34a20bf849f4e6a.png

10148 ms

8b7dc7714b4fdeaff69c54c2f9275ca5.png

8b7dc7714b4fdeaff69c54c2f9275ca5.png

10750 ms

882edc1a8553250157347e674df7e2ab.jpg

882edc1a8553250157347e674df7e2ab.jpg

11716 ms

a3ad36640d6d2731a0c196fc8b574f6c.png

a3ad36640d6d2731a0c196fc8b574f6c.png

11876 ms

softwarebtn3.png

softwarebtn3.png

13286 ms

softwarebtn1.png

softwarebtn1.png

13437 ms

softwarebtn2.png

softwarebtn2.png

13746 ms

61288212a6c4f.png

61288212a6c4f.png

16672 ms

6128828ce3338.png

6128828ce3338.png

15442 ms

612882a54aa09.png

612882a54aa09.png

16684 ms

612882bc3cfac.png

612882bc3cfac.png

16302 ms

technology_logo.png

technology_logo.png

15082 ms

technology_icon1.png

technology_icon1.png

15675 ms

technology_icon2.png

technology_icon2.png

15664 ms

technology_icon3.png

technology_icon3.png

15768 ms

technology_icon4.png

technology_icon4.png

16126 ms

62c535ce9f0a6.jpg

62c535ce9f0a6.jpg

16912 ms

62a0562f3ea99.png

62a0562f3ea99.png

18060 ms

layer.css

layer.css

16379 ms

hm.gif

hm.gif

311 ms

b.js

b.js

1698 ms

62a1be9536b41.jpg

62a1be9536b41.jpg

20017 ms

6196198159d97.png

6196198159d97.png

17135 ms

6194ce6c8e4c7.png

6194ce6c8e4c7.png

17480 ms

service_icons1.png

service_icons1.png

16429 ms

service_icons2.png

service_icons2.png

16912 ms

service_icons3.png

service_icons3.png

17101 ms

brandimgs4.png

brandimgs4.png

17129 ms

brandimgs2.png

brandimgs2.png

17118 ms

softwarebtn33.png

softwarebtn33.png

18254 ms

softwarebtn11.png

softwarebtn11.png

18299 ms

affim.js

affim.js

2113 ms

softwarebtn22.png

softwarebtn22.png

14508 ms

base_foot.png

base_foot.png

11025 ms

phone.png

phone.png

10160 ms

spein_tel2.png

spein_tel2.png

10132 ms

spein_person2.png

spein_person2.png

9711 ms

spein_top3.png

spein_top3.png

9216 ms

search-icon.png

search-icon.png

9073 ms

top_icon.png

top_icon.png

8958 ms

right-btn.png

right-btn.png

7932 ms

left-btn.png

left-btn.png

8075 ms

harder-icon.png

harder-icon.png

7859 ms

pro-icon.png

pro-icon.png

8011 ms

service_phone.png

service_phone.png

7395 ms

spein_top.png

spein_top.png

6729 ms

layer.js

layer.js

4764 ms

Accessibility Review

twinflag.com accessibility score

70

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

twinflag.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

twinflag.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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

    EN

  • Encoding

    UTF-8

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

twinflag.com

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