Tools & Wizards About Us
couriers.glovoapp.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

couriers.glovoapp.com

Glovo Couriers

Page Load Speed

1.3 sec in total

First Response

14 ms

Resources Loaded

1.1 sec

Page Rendered

147 ms

couriers.glovoapp.com screenshot

About Website

Click here to check amazing Couriers Glovo App content for Poland. Otherwise, check out these important facts you probably never knew about couriers.glovoapp.com

Visit couriers.glovoapp.com

Key Findings

We analyzed Couriers.glovoapp.com page load time and found that the first response time was 14 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

couriers.glovoapp.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

96/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value3,390 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

couriers.glovoapp.com

14 ms

couriers.glovoapp.com

196 ms

polyfill.min.js

820 ms

am.png

68 ms

state.js

172 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 41% of them (18 requests) were addressed to the original Couriers.glovoapp.com, 50% (22 requests) were made to Glovo.dhmedia.io and 7% (3 requests) were made to Glovo-fonts-78305bac.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (820 ms) relates to the external source Cdnjs.cloudflare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.5 kB (21%)

Content Size

575.4 kB

After Optimization

455.9 kB

  • HTML
  • JavaScript

In fact, the total size of Couriers.glovoapp.com main page is 575.4 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. 30% of websites need less resources to load. Javascripts take 437.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 118.2 kB

  • Original 137.6 kB
  • After minification 137.5 kB
  • After compression 19.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 118.2 kB or 86% of the original size.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 437.8 kB
  • After minification 437.8 kB
  • After compression 436.5 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 12 (31%)

Requests Now

39

After Optimization

27

  • Images
  • JavaScript

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

Network Requests Diagram

couriers.glovoapp.com

couriers.glovoapp.com

14 ms

couriers.glovoapp.com

couriers.glovoapp.com

196 ms

polyfill.min.js

polyfill.min.js

820 ms

am.png

am.png

68 ms

state.js

state.js

172 ms

ce8ce1b.js

ce8ce1b.js

212 ms

a9c9b46.js

a9c9b46.js

215 ms

7c8cf1d.js

7c8cf1d.js

226 ms

228f676.js

228f676.js

209 ms

44da1ac.js

44da1ac.js

212 ms

9e725c1.js

9e725c1.js

335 ms

31c9212.js

31c9212.js

387 ms

0c04394.js

0c04394.js

374 ms

6b8b3d1.js

6b8b3d1.js

387 ms

955c36a.js

955c36a.js

386 ms

e437dc1.js

e437dc1.js

402 ms

ba.png

ba.png

64 ms

bg.png

bg.png

65 ms

ci.png

ci.png

68 ms

es.png

es.png

64 ms

ge.png

ge.png

66 ms

hr.png

hr.png

68 ms

it.png

it.png

71 ms

ke.png

ke.png

70 ms

kg.png

kg.png

71 ms

kz.png

kz.png

187 ms

ma.png

ma.png

200 ms

md.png

md.png

183 ms

me.png

me.png

194 ms

ng.png

ng.png

184 ms

pl.png

pl.png

183 ms

pt.png

pt.png

304 ms

ro.png

ro.png

315 ms

rs.png

rs.png

287 ms

tn.png

tn.png

371 ms

ua.png

ua.png

305 ms

ug.png

ug.png

383 ms

glovo-logo-light.4661a76.svg

glovo-logo-light.4661a76.svg

504 ms

logo.b0f6ef1.svg

logo.b0f6ef1.svg

471 ms

app-store.6eda51f.svg

app-store.6eda51f.svg

552 ms

play-store.6ceb4bf.svg

play-store.6ceb4bf.svg

564 ms

GlovoSans-Book.woff

GlovoSans-Book.woff

442 ms

GlovoSans-Medium.woff

GlovoSans-Medium.woff

479 ms

GlovoSans-Bold.woff

GlovoSans-Bold.woff

506 ms

Accessibility Review

couriers.glovoapp.com accessibility score

90

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

Image elements do not have [alt] attributes

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

couriers.glovoapp.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

couriers.glovoapp.com SEO score

64

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

High

Document doesn't have a valid hreflang

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

    EN

  • Encoding

    N/A

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

couriers.glovoapp.com

Open Graph description is not detected on the main page of Couriers Glovo App. 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: