Tools & Wizards About Us
wedely.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

wedely.com

WeDely.com | Food Delivery | Made in Luxembourg | Livraison de Repas à Domicile

Page Load Speed

4.5 sec in total

First Response

228 ms

Resources Loaded

4.1 sec

Page Rendered

172 ms

wedely.com screenshot

About Website

Visit wedely.com now to see the best up-to-date We Dely content for Luxembourg and also check out these interesting facts you probably never knew about wedely.com

You don't know what to eat today? Order online what you desire! High-quality fresh food for takeaway or home delivery in Luxembourg. Faites-vous livrer à domicile tous les plats de vos restaurants pré...

Visit wedely.com

Key Findings

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

Performance Metrics

wedely.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

wedely.com

228 ms

www.wedely.com

276 ms

www.wedely.com

489 ms

css

48 ms

bootstrap.min.css

397 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 85% of them (56 requests) were addressed to the original Wedely.com, 9% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Wedely.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.6 kB (7%)

Content Size

565.7 kB

After Optimization

528.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wedely.com main page is 565.7 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. 60% of websites need less resources to load. Images take 350.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 22.6 kB

  • Original 30.6 kB
  • After minification 30.6 kB
  • After compression 7.9 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 22.6 kB or 74% of the original size.

Image Optimization

-4%

Potential reduce by 12.7 kB

  • Original 350.4 kB
  • After minification 337.8 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. We Dely images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.3 kB

  • Original 184.7 kB
  • After minification 184.7 kB
  • After compression 182.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 42 (75%)

Requests Now

56

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wedely.com

wedely.com

228 ms

www.wedely.com

www.wedely.com

276 ms

www.wedely.com

www.wedely.com

489 ms

css

css

48 ms

bootstrap.min.css

bootstrap.min.css

397 ms

font-awesome.min.css

font-awesome.min.css

313 ms

simple-line-icons.min.css

simple-line-icons.min.css

322 ms

owl.carousel.min.css

owl.carousel.min.css

319 ms

owl.theme.default.min.css

owl.theme.default.min.css

317 ms

magnific-popup.min.css

magnific-popup.min.css

316 ms

theme.css

theme.css

607 ms

theme-elements.css

theme-elements.css

714 ms

settings.css

settings.css

629 ms

layers.min.css

layers.min.css

613 ms

navigation.min.css

navigation.min.css

632 ms

component.min.css

component.min.css

682 ms

default.min.css

default.min.css

897 ms

custom.css

custom.css

907 ms

modernizr.min.js

modernizr.min.js

917 ms

js

js

79 ms

jquery-ui.min.css

jquery-ui.min.css

916 ms

jquery.min.js

jquery.min.js

1107 ms

jquery.appear.min.js

jquery.appear.min.js

1105 ms

jquery.easing.min.js

jquery.easing.min.js

1235 ms

jquery.stellar.min.js

jquery.stellar.min.js

1299 ms

bootstrap.min.js

bootstrap.min.js

1304 ms

common.js

common.js

1297 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1398 ms

jquery-ui.min.js

jquery-ui.min.js

1397 ms

theme.js

theme.js

1531 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1697 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1687 ms

jquery.flipshow.min.js

jquery.flipshow.min.js

1586 ms

ios7-switch.js

ios7-switch.js

1685 ms

jquery.pulse.min.js

jquery.pulse.min.js

1687 ms

custom.js

custom.js

1834 ms

theme.init.js

theme.init.js

1876 ms

save.js

save.js

1975 ms

mobileSwitch.js

mobileSwitch.js

2020 ms

gtm.js

gtm.js

176 ms

logo-white-wedely.png

logo-white-wedely.png

1110 ms

morethanfood.png

morethanfood.png

1058 ms

en_US.png

en_US.png

1219 ms

lu_LU.png

lu_LU.png

1222 ms

fr_FR.png

fr_FR.png

1322 ms

de_DE.png

de_DE.png

1346 ms

pt_PT.png

pt_PT.png

1356 ms

it_IT.png

it_IT.png

1405 ms

es_ES.png

es_ES.png

1502 ms

made_in_lux.png

made_in_lux.png

1606 ms

slide-bg-5.jpg

slide-bg-5.jpg

1808 ms

slide-bg-4.jpg

slide-bg-4.jpg

1837 ms

slide-bg-6.jpg

slide-bg-6.jpg

1933 ms

app_store.svg

app_store.svg

1550 ms

google-play.png

google-play.png

1657 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

90 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

99 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

126 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

159 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

160 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1939 ms

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf

UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf

159 ms

fbevents.js

fbevents.js

69 ms

revolution.extension.slideanims.min.js

revolution.extension.slideanims.min.js

900 ms

revolution.extension.layeranimation.min.js

revolution.extension.layeranimation.min.js

1018 ms

revolution.extension.navigation.min.js

revolution.extension.navigation.min.js

1021 ms

Accessibility Review

wedely.com accessibility score

67

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

wedely.com best practices score

75

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

SEO Factors

wedely.com SEO score

81

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    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 Wedely.com 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 Wedely.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

wedely.com

Open Graph data is detected on the main page of We Dely. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: