Report Summary

  • 0

    Performance

  • 34

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

lisal.me

lisal.me - Registered at Namecheap.com

Page Load Speed

2.5 sec in total

First Response

314 ms

Resources Loaded

1.2 sec

Page Rendered

945 ms

lisal.me screenshot

About Website

Welcome to lisal.me homepage info - get ready to check Lisal best content right away, or after learning these important things about lisal.me

客家姑娘,書寫生活

Visit lisal.me

Key Findings

We analyzed Lisal.me page load time and found that the first response time was 314 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

lisal.me 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.072

96/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

lisal.me

314 ms

jquery.fancybox.css

278 ms

css

26 ms

font-awesome.min.css

252 ms

main.css

235 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 81% of them (22 requests) were addressed to the original Lisal.me, 15% (4 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (592 ms) belongs to the original domain Lisal.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.2 kB (73%)

Content Size

118.8 kB

After Optimization

32.6 kB

In fact, the total size of Lisal.me main page is 118.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. 45% of websites need less resources to load. CSS take 73.5 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 28.3 kB

  • Original 45.3 kB
  • After minification 40.0 kB
  • After compression 17.0 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 5.3 kB, which is 12% 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 28.3 kB or 62% of the original size.

CSS Optimization

-79%

Potential reduce by 57.9 kB

  • Original 73.5 kB
  • After minification 65.3 kB
  • After compression 15.6 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. Lisal.me needs all CSS files to be minified and compressed as it can save up to 57.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (86%)

Requests Now

14

After Optimization

2

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

Accessibility Review

lisal.me accessibility score

34

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

Document doesn't have a <title> element

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

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

lisal.me 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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lisal.me SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lisal.me 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 Lisal.me 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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: