4.6 sec in total
966 ms
3.1 sec
531 ms
Click here to check amazing L 38 content. Otherwise, check out these important facts you probably never knew about l38.net
外汇走势研究室-01-22年记录
Visit l38.netWe analyzed L38.net page load time and found that the first response time was 966 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
l38.net performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.001
100/100
15%
Value0
0/100
10%
966 ms
239 ms
354 ms
339 ms
1441 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 47% of them (28 requests) were addressed to the original L38.net, 51% (30 requests) were made to Y2.cn and 2% (1 request) were made to 0. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Y2.cn.
Page size can be reduced by 223.2 kB (56%)
401.8 kB
178.6 kB
In fact, the total size of L38.net main page is 401.8 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. Javascripts take 167.8 kB which makes up the majority of the site volume.
Potential reduce by 37.2 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 37.2 kB or 81% of the original size.
Potential reduce by 26.7 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. Obviously, L 38 needs image optimization as it can save up to 26.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 115.0 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 115.0 kB or 69% of the original size.
Potential reduce by 44.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. L38.net needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 77% of the original size.
Number of requests can be reduced by 4 (7%)
58
54
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L 38. 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 as a result speed up the page load time.
l38.net
966 ms
style_1_common.css
239 ms
common.js
354 ms
portal.js
339 ms
api.php
1441 ms
api.php
1373 ms
api.php
1374 ms
api.php
1376 ms
background.png
64 ms
logo.png
63 ms
hd_shadow.png
63 ms
sc.png
63 ms
indexquote.php
110 ms
search.png
109 ms
pt_item.png
115 ms
bs_6_ft.png
116 ms
bs_6_hd.png
123 ms
bs_6_ft_r.png
123 ms
table.css
63 ms
jquery-1.8.3.min.js
188 ms
ws.js
69 ms
table.min.js
70 ms
allData
523 ms
bg-table-caption.png
64 ms
bg-table-head.jpg
64 ms
state-offline.gif
65 ms
state-online.gif
71 ms
dot.gif
62 ms
111641nbvod5bvqtthfdt6.png
187 ms
001510xzc16hhdkmws16ww.gif
187 ms
214817ftfthohw46hzaag9.gif
165 ms
224249oqmmfznynrnznapf.gif
255 ms
082230kpgyyhn0bhnnnpyp.gif
314 ms
103821wz0gq8kg7obqbupl.gif
318 ms
bs_2_ft.png
67 ms
bs_2_hd.png
68 ms
bs_2_ft_r.png
66 ms
sortnum.png
63 ms
scrolltop.png
63 ms
noavatar_small.gif
268 ms
72_avatar_small.jpg
250 ms
05_avatar_small.jpg
254 ms
41_avatar_small.jpg
216 ms
58_avatar_small.jpg
198 ms
36_avatar_small.jpg
226 ms
01_avatar_small.jpg
239 ms
09_avatar_small.jpg
207 ms
77_avatar_small.jpg
194 ms
noavatar_small.gif
195 ms
noavatar_small.gif
191 ms
61_avatar_small.jpg
219 ms
noavatar_small.gif
237 ms
06_avatar_small.jpg
205 ms
81_avatar_small.jpg
193 ms
noavatar_small.gif
192 ms
09_avatar_small.jpg
191 ms
57_avatar_small.jpg
218 ms
53_avatar_small.jpg
236 ms
noavatar_small.gif
206 ms
l38.net accessibility score
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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
l38.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
l38.net SEO score
EN
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L38.net can be misinterpreted by Google and other search engines. Our service has detected that English 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 L38.net main page’s claimed encoding is gbk. 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.
l38.net
Open Graph description is not detected on the main page of L 38. 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: