Tools & Wizards About Us
lalolarestaurante.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lalolarestaurante.com

Grupo LaLoLa

Page Load Speed

8.1 sec in total

First Response

1.6 sec

Resources Loaded

6.3 sec

Page Rendered

204 ms

lalolarestaurante.com screenshot

About Website

Visit lalolarestaurante.com now to see the best up-to-date La Lo Restaurante content for Spain and also check out these interesting facts you probably never knew about lalolarestaurante.com

Visit lalolarestaurante.com

Key Findings

We analyzed Lalolarestaurante.com page load time and found that the first response time was 1.6 sec and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lalolarestaurante.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value31.4 s

0/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value29.7 s

0/100

10%

Network Requests Diagram

lalolarestaurante.com

1591 ms

js

58 ms

js

115 ms

gtm.js

143 ms

bc17cc60eee2bb2d78073ed364bfefe4.css

797 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 56% of them (32 requests) were addressed to the original Lalolarestaurante.com, 16% (9 requests) were made to Fonts.gstatic.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Lalolarestaurante.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (60%)

Content Size

5.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lalolarestaurante.com main page is 5.2 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. CSS take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 44.4 kB

  • Original 57.8 kB
  • After minification 57.6 kB
  • After compression 13.4 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 44.4 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 56.3 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. La Lo Restaurante images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 854.2 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 609.4 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 854.2 kB or 58% of the original size.

CSS Optimization

-90%

Potential reduce by 2.1 MB

  • Original 2.3 MB
  • After minification 2.3 MB
  • After compression 223.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. Lalolarestaurante.com needs all CSS files to be minified and compressed as it can save up to 2.1 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (70%)

Requests Now

46

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lalolarestaurante.com

lalolarestaurante.com

1591 ms

js

js

58 ms

js

js

115 ms

gtm.js

gtm.js

143 ms

bc17cc60eee2bb2d78073ed364bfefe4.css

bc17cc60eee2bb2d78073ed364bfefe4.css

797 ms

jquery.min.js

jquery.min.js

644 ms

3c55530377b06db487865ed78f7dcaa0.js

3c55530377b06db487865ed78f7dcaa0.js

362 ms

132a5da467e8225723575fa831bd1647.js

132a5da467e8225723575fa831bd1647.js

487 ms

8844f1a3bb9ab5ccf5bc73646d274091.js

8844f1a3bb9ab5ccf5bc73646d274091.js

360 ms

9f0b52a32d120fcd71c1106384c6ec8c.js

9f0b52a32d120fcd71c1106384c6ec8c.js

358 ms

ea29ab5e48204ef2c8487914a0067048.js

ea29ab5e48204ef2c8487914a0067048.js

470 ms

197af4cb455bab8aca5acd98096738e5.js

197af4cb455bab8aca5acd98096738e5.js

481 ms

e45a780e9a91b7fa3dea866dfee4cb1c.js

e45a780e9a91b7fa3dea866dfee4cb1c.js

497 ms

27a80c1a1a423f6b775f7aaae635b77c.js

27a80c1a1a423f6b775f7aaae635b77c.js

910 ms

5d0a987612eefe578c43cc868f1bb75e.js

5d0a987612eefe578c43cc868f1bb75e.js

1460 ms

c866d5fdca6a52f7bde70c5b4606a803.js

c866d5fdca6a52f7bde70c5b4606a803.js

953 ms

ccdfb5f339eb601f80130699b57fddae.js

ccdfb5f339eb601f80130699b57fddae.js

617 ms

7f99284a0be54b3e2f93f9df69ab57f1.js

7f99284a0be54b3e2f93f9df69ab57f1.js

907 ms

5f232a28d0e164f035194481960cf56b.js

5f232a28d0e164f035194481960cf56b.js

790 ms

c635d8aaccf129af33c15a6e9e09c1fe.js

c635d8aaccf129af33c15a6e9e09c1fe.js

1208 ms

ea7f9fba508e1d59cc2c53911336425b.js

ea7f9fba508e1d59cc2c53911336425b.js

908 ms

e944526a5cb2324b1ab86cc7842647a3.js

e944526a5cb2324b1ab86cc7842647a3.js

922 ms

1daf0780626dd619bc4ac36f010777da.js

1daf0780626dd619bc4ac36f010777da.js

1019 ms

b12f1857e1dfd155ed77af59426d7dd2.js

b12f1857e1dfd155ed77af59426d7dd2.js

1024 ms

f2e0f337bda2c4ef650c82f684a15fd6.js

f2e0f337bda2c4ef650c82f684a15fd6.js

1187 ms

aaf4c8c9277a832a6c697ca1602fa418.js

aaf4c8c9277a832a6c697ca1602fa418.js

1068 ms

305f724f9d5dcef06e402db53bf298c4.js

305f724f9d5dcef06e402db53bf298c4.js

1130 ms

analytics.js

analytics.js

17 ms

js

js

116 ms

collect

collect

30 ms

webfont.js

webfont.js

57 ms

Lalola-web-1.jpg

Lalola-web-1.jpg

281 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

24 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

37 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

42 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

50 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

46 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

425 ms

css

css

50 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xA.woff

4 ms

recaptcha__en.js

recaptcha__en.js

59 ms

LaLola.jpg

LaLola.jpg

182 ms

Colmado-LaLola-1.jpg

Colmado-LaLola-1.jpg

1049 ms

anchor

anchor

55 ms

styles__ltr.css

styles__ltr.css

4 ms

recaptcha__en.js

recaptcha__en.js

11 ms

OS4jJSgmcHxk24mPNVLLuJfLsxLv_4nnTDIIah-C-70.js

OS4jJSgmcHxk24mPNVLLuJfLsxLv_4nnTDIIah-C-70.js

46 ms

webworker.js

webworker.js

45 ms

logo_48.png

logo_48.png

33 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

17 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

17 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

17 ms

recaptcha__en.js

recaptcha__en.js

16 ms

PARKING-GRATIS-PARA-WEB.jpg

PARKING-GRATIS-PARA-WEB.jpg

112 ms

ingles-horizontal-transparente-1024x428.png

ingles-horizontal-transparente-1024x428.png

339 ms

Sin-titulo-400-x-250-px.png

Sin-titulo-400-x-250-px.png

523 ms

generalitat-300x146.png

generalitat-300x146.png

139 ms

Accessibility Review

lalolarestaurante.com accessibility score

95

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

lalolarestaurante.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lalolarestaurante.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lalolarestaurante.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Lalolarestaurante.com 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

lalolarestaurante.com

Open Graph description is not detected on the main page of La Lo Restaurante. 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: