Tools & Wizards About Us
forlinx.com screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

forlinx.com

飞凌嵌入式官网-ARM嵌入式核心板、开发板、工控机、工业网关解决方案-专注智能设备核心平台研发与制造 - 保定飞凌嵌入式技术有限公司

Page Load Speed

15.4 sec in total

First Response

1.9 sec

Resources Loaded

12.4 sec

Page Rendered

1.1 sec

forlinx.com screenshot

About Website

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

飞凌嵌入式专注ARM嵌入式解决方案，基于瑞芯微、NXP、TI、全志等主流芯片平台（RK3568、RK3588、RK3576、T536、T113i），提供从Cortex-A7到Cortex-A72系列的核心板、开发板、工业主板及工业网关。支持Android、Linux、Ubuntu、RTOS系统，广泛应用于工业物联网、智慧电力、医疗设备、交通环保等领域，并提供ODM/OEM深度定制服务。

Visit forlinx.com

Key Findings

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

forlinx.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.8 s

8/100

10%

Network Requests Diagram

www.forlinx.com

1939 ms

chanzhi.all.css

256 ms

default_wide_zh-cn.css

499 ms

chanzhi.all.js

1190 ms

source-css-28021b7593bb64d6bd25b51a5d881c87-1719471884.html

775 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 96% of them (51 requests) were addressed to the original Forlinx.com, 4% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (8.3 sec) belongs to the original domain Forlinx.com.

Page Optimization Overview & Recommendations

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

Content Size

6.9 MB

After Optimization

6.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 74.8 kB

  • Original 86.5 kB
  • After minification 45.3 kB
  • After compression 11.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 41.3 kB, which is 48% 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 74.8 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 37.4 kB

  • Original 6.5 MB
  • After minification 6.4 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. Forlinx images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 102.0 kB

  • Original 210.5 kB
  • After minification 210.5 kB
  • After compression 108.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 102.0 kB or 48% of the original size.

CSS Optimization

-52%

Potential reduce by 68.0 kB

  • Original 131.9 kB
  • After minification 113.2 kB
  • After compression 63.9 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. Forlinx.com needs all CSS files to be minified and compressed as it can save up to 68.0 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (22%)

Requests Now

50

After Optimization

39

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forlinx. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.forlinx.com

www.forlinx.com

1939 ms

chanzhi.all.css

chanzhi.all.css

256 ms

default_wide_zh-cn.css

default_wide_zh-cn.css

499 ms

chanzhi.all.js

chanzhi.all.js

1190 ms

source-css-28021b7593bb64d6bd25b51a5d881c87-1719471884.html

source-css-28021b7593bb64d6bd25b51a5d881c87-1719471884.html

775 ms

main.css

main.css

740 ms

animate.min.css

animate.min.css

747 ms

swiper-bundle.min.css

swiper-bundle.min.css

749 ms

video.css

video.css

743 ms

style.css

style.css

988 ms

swiper-bundle.min.js

swiper-bundle.min.js

998 ms

wow.js

wow.js

991 ms

javascript.js

javascript.js

1003 ms

source-js-28021b7593bb64d6bd25b51a5d881c87-1719471884.html

source-js-28021b7593bb64d6bd25b51a5d881c87-1719471884.html

1050 ms

hm.js

hm.js

1191 ms

logo.png

logo.png

243 ms

icon-arrow-down.png

icon-arrow-down.png

237 ms

icon-search.png

icon-search.png

236 ms

file.php

file.php

1874 ms

file.php

file.php

2956 ms

file.php

file.php

2654 ms

file.php

file.php

3154 ms

file.php

file.php

8310 ms

file.php

file.php

3869 ms

tc_close.png

tc_close.png

2108 ms

file.php

file.php

2817 ms

file.php

file.php

3135 ms

file.php

file.php

3056 ms

file.php

file.php

3202 ms

file.php

file.php

3293 ms

file.php

file.php

4339 ms

file.php

file.php

5507 ms

file.php

file.php

3693 ms

icon-more.png

icon-more.png

3525 ms

file.php

file.php

4700 ms

file.php

file.php

4427 ms

file.php

file.php

4352 ms

file.php

file.php

4820 ms

icon-wx.png

icon-wx.png

4593 ms

icon-tb.png

icon-tb.png

4669 ms

icon-tm.png

icon-tm.png

4837 ms

wechat-ewm.png

wechat-ewm.png

5159 ms

phone.png

phone.png

4931 ms

icon_02.png

icon_02.png

5059 ms

chat.png

chat.png

5076 ms

icon_03.png

icon_03.png

5166 ms

icon_04.png

icon_04.png

5299 ms

arrow.png

arrow.png

5316 ms

icon-play2.png

icon-play2.png

5361 ms

case-bg.jpg

case-bg.jpg

6294 ms

border-bg.jpg

border-bg.jpg

5499 ms

zenicon.woff

zenicon.woff

5575 ms

hm.gif

hm.gif

330 ms

Accessibility Review

forlinx.com accessibility score

85

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

Best Practices

forlinx.com best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

forlinx.com SEO score

78

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

    ZH

  • Encoding

    UTF-8

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

forlinx.com

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