74.5 sec in total
9.9 sec
64.3 sec
297 ms
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
飞凌嵌入式提供瑞芯微、全志、TI、NXP、瑞萨等ARM开发板,ARM工控板,提供Android、Linux、RTOS等系统工业主板,提供Cortex-A7、Cortex-A53、Cortex-A72等系列arm核心板,开发板,提供基于RK3568、RK3588、RK3399、iMX9352、imx6、imx6q、imx6dl、imx6ul、imx8mm、ls1046a、ls1043a、ls1012...
Visit forlinx.comWe analyzed Forlinx.com page load time and found that the first response time was 9.9 sec and then it took 64.6 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. Unfortunately, there were 27 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
forlinx.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.0 s
6/100
25%
Value20.8 s
0/100
10%
Value220 ms
87/100
30%
Value0.328
35/100
15%
Value5.9 s
66/100
10%
9893 ms
9715 ms
20083 ms
7331 ms
949 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 67% of them (50 requests) were addressed to the original Forlinx.com, 8% (6 requests) were made to Skin.54kefu.net and 5% (4 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Forlinx.com.
Page size can be reduced by 28.8 kB (68%)
42.5 kB
13.7 kB
In fact, the total size of Forlinx.com main page is 42.5 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. HTML takes 20.7 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.8 kB or 72% of the original size.
Potential reduce by 11.6 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 11.6 kB or 62% of the original size.
Potential reduce by 2.4 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 2.4 kB or 78% of the original size.
Number of requests can be reduced by 32 (68%)
47
15
The browser has sent 47 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 11 to 1 for JavaScripts and as a result speed up the page load time.
forlinx.com
9893 ms
css.css
9715 ms
jquery.min.js
20083 ms
banner.js
7331 ms
kuaixun.js
949 ms
891387.js
2688 ms
z_stat.php
986 ms
logo.gif
4192 ms
t_r10.gif
1773 ms
t_r11.gif
1787 ms
t_rxx.gif
458 ms
t_r12.gif
3708 ms
search.gif
929 ms
t_r15.gif
2721 ms
t_r2.gif
4051 ms
pic1.gif
8506 ms
pic2.gif
3572 ms
pic3.gif
4536 ms
pic4.gif
4349 ms
pic5.gif
7996 ms
an1.gif
4977 ms
more.gif
4680 ms
41597897.jpg
19992 ms
40807565.jpg
19993 ms
37941401.jpg
19993 ms
38036637.jpg
19993 ms
38072405.jpg
19994 ms
51561205.jpg
19994 ms
38404541.jpg
19994 ms
38497981.jpg
19995 ms
tj.gif
19995 ms
more2.gif
19995 ms
lx.gif
19994 ms
tel.gif
19995 ms
lx2.gif
19996 ms
news.gif
19995 ms
zl.gif
19996 ms
dd.gif
19996 ms
top.gif
19997 ms
f1.gif
19997 ms
wei.gif
19996 ms
xin.gif
19996 ms
stat.htm
162 ms
core.php
1295 ms
9.gif
19710 ms
pic.gif
787 ms
getonline
15496 ms
891387_code.js
1027 ms
url.js
1028 ms
T1FXHXXahjXXXAK3zo-77-18.gif
260 ms
skin.css
1143 ms
top.gif
1208 ms
2_f.gif
1256 ms
bottom.gif
3412 ms
hm.js
628 ms
t_r1.gif
2225 ms
s1.gif
2044 ms
nav1.gif
2046 ms
32436175.jpg
20053 ms
71839505.jpg
20054 ms
53876481.jpg
20057 ms
59726997.jpg
20058 ms
47844309.jpg
20058 ms
ff.gif
4802 ms
h.js
607 ms
middle.gif
480 ms
r.gif
5033 ms
hm.gif
247 ms
21.gif
673 ms
lxb.js
2161 ms
hm.gif
249 ms
nopic.gif
4474 ms
log.gif
1286 ms
_l.js
952 ms
log.gif
418 ms
forlinx.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
forlinx.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
forlinx.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
ZH
N/A
GB2312
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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Forlinx.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.
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: