Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

l38.net

www.l38.net-官网首页

Page Load Speed

4.6 sec in total

First Response

966 ms

Resources Loaded

3.1 sec

Page Rendered

531 ms

l38.net screenshot

About Website

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.net

Key Findings

We 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.

Performance Metrics

l38.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

l38.net

966 ms

style_1_common.css

239 ms

common.js

354 ms

portal.js

339 ms

api.php

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 Optimization Overview & Recommendations

Page size can be reduced by 223.2 kB (56%)

Content Size

401.8 kB

After Optimization

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.

HTML Optimization

-81%

Potential reduce by 37.2 kB

  • Original 45.9 kB
  • After minification 45.1 kB
  • After compression 8.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. 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.

Image Optimization

-20%

Potential reduce by 26.7 kB

  • Original 130.7 kB
  • After minification 104.1 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.

JavaScript Optimization

-69%

Potential reduce by 115.0 kB

  • Original 167.8 kB
  • After minification 154.7 kB
  • After compression 52.8 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.

CSS Optimization

-77%

Potential reduce by 44.4 kB

  • Original 57.4 kB
  • After minification 55.7 kB
  • After compression 13.0 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.

Requests Breakdown

Number of requests can be reduced by 4 (7%)

Requests Now

58

After Optimization

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.

Accessibility Review

l38.net accessibility score

68

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

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

l38.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

l38.net SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: