Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

lalin.org

Bienvenidos | Lalín, quilómetro cero de Galicia

Page Load Speed

1.3 sec in total

First Response

568 ms

Resources Loaded

583 ms

Page Rendered

169 ms

lalin.org screenshot

About Website

Welcome to lalin.org homepage info - get ready to check Lalin best content right away, or after learning these important things about lalin.org

Visit lalin.org

Key Findings

We analyzed Lalin.org page load time and found that the first response time was 568 ms and then it took 752 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

lalin.org performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value25.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value32.4 s

0/100

25%

SI (Speed Index)

Value33.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,090 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value41.7 s

0/100

10%

Network Requests Diagram

lalin.org

568 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Lalin.org and no external sources were called. The less responsive or slowest element that took the longest time to load (568 ms) belongs to the original domain Lalin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 179 B (40%)

Content Size

450 B

After Optimization

271 B

In fact, the total size of Lalin.org main page is 450 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 450 B which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 179 B

  • Original 450 B
  • After minification 443 B
  • After compression 271 B

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 179 B or 40% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

lalin.org accessibility score

65

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

High

[aria-*] attributes do not have valid values

High

[aria-*] attributes are not valid or misspelled

High

ARIA IDs are not unique

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

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

lalin.org 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

lalin.org SEO score

99

Search Engine Optimization Advices

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

    GL

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lalin.org can be misinterpreted by Google and other search engines. Our service has detected that Galician 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 Lalin.org main page’s claimed encoding is iso-8859-1. 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 Lalin. 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: