Tools & Wizards About Us
get.peoople.co screenshot

Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

get.peoople.co

Peoople • The best recommendations from your friends and favorite influencers

Page Load Speed

2.6 sec in total

First Response

303 ms

Resources Loaded

2.1 sec

Page Rendered

268 ms

get.peoople.co screenshot

About Website

Visit get.peoople.co now to see the best up-to-date Get Peoople content for Spain and also check out these interesting facts you probably never knew about get.peoople.co

Peoople is the app to discover the best and latest recommendations on restaurants, movies, series and much more thanks to your friends and favorite influencers

Visit get.peoople.co

Key Findings

We analyzed Get.peoople.co page load time and found that the first response time was 303 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

get.peoople.co performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

74/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.2 s

95/100

10%

Network Requests Diagram

peoople.app

303 ms

en

494 ms

fonts.css

139 ms

svg-with-js.css

157 ms

branch-2.47.1.min.js

18 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Get.peoople.co, 9% (3 requests) were made to Cdn.peoople.app and 6% (2 requests) were made to Config.metomic.io. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Peoople.app.

Page Optimization Overview & Recommendations

Page size can be reduced by 376.8 kB (53%)

Content Size

712.4 kB

After Optimization

335.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Get.peoople.co main page is 712.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. 40% of websites need less resources to load. HTML takes 450.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 376.7 kB

  • Original 450.7 kB
  • After minification 450.7 kB
  • After compression 74.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. 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 376.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 239.1 kB
  • After minification 239.1 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. Get Peoople images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 132 B

  • Original 21.2 kB
  • After minification 21.2 kB
  • After compression 21.1 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.

CSS Optimization

-1%

Potential reduce by 13 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 1.3 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. Get.peoople.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 21 (78%)

Requests Now

27

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Get Peoople. 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 as a result speed up the page load time.

Network Requests Diagram

peoople.app

peoople.app

303 ms

en

en

494 ms

fonts.css

fonts.css

139 ms

svg-with-js.css

svg-with-js.css

157 ms

branch-2.47.1.min.js

branch-2.47.1.min.js

18 ms

config.js

config.js

4 ms

polyfills-d1dff7bbd80c1e25f7a2.js

polyfills-d1dff7bbd80c1e25f7a2.js

223 ms

main-62b6d6388d9fcc5905dc.js

main-62b6d6388d9fcc5905dc.js

146 ms

webpack-eb080e3f091731f228fb.js

webpack-eb080e3f091731f228fb.js

228 ms

framework.8e5c69f33a052d0b8795.js

framework.8e5c69f33a052d0b8795.js

349 ms

ea88be26.1affd7e70586768efa2b.js

ea88be26.1affd7e70586768efa2b.js

423 ms

29107295.b6b867ec19984a86515e.js

29107295.b6b867ec19984a86515e.js

305 ms

75fc9c18.242b027f625fd9a3ad8d.js

75fc9c18.242b027f625fd9a3ad8d.js

241 ms

a9a7754c.361891a11cb41f6b69a2.js

a9a7754c.361891a11cb41f6b69a2.js

586 ms

commons.06b582ee4c1fa4d3fbc9.js

commons.06b582ee4c1fa4d3fbc9.js

376 ms

911ac972f99d841c7294b25ba445883697974c7d.d0785406d34aa68b1d2e.js

911ac972f99d841c7294b25ba445883697974c7d.d0785406d34aa68b1d2e.js

1097 ms

dca3cbde72d8dc7bd165795f0002c6b801c63597.5079f280c8b5930c5999.js

dca3cbde72d8dc7bd165795f0002c6b801c63597.5079f280c8b5930c5999.js

423 ms

326103e19c9905f94994ff5c5676f5490b8986a0.9749144aee7de2b049a6.js

326103e19c9905f94994ff5c5676f5490b8986a0.9749144aee7de2b049a6.js

575 ms

f87614ab117cead8b452422622d828952fa8608a.f11651ec42824ed2dff6.js

f87614ab117cead8b452422622d828952fa8608a.f11651ec42824ed2dff6.js

653 ms

e7e391aae947704310518375384d04364853aefd.118a9211b416d7c3c912.js

e7e391aae947704310518375384d04364853aefd.118a9211b416d7c3c912.js

588 ms

434ef95f0ce12dc96f2b45dab38ad6bc02493cbb.ffaffe88f8522e42ee35.js

434ef95f0ce12dc96f2b45dab38ad6bc02493cbb.ffaffe88f8522e42ee35.js

583 ms

be9a8ae375b5f55bb573b66fafd0c667e6d4b909.a9ac85e58307d0375fe4.js

be9a8ae375b5f55bb573b66fafd0c667e6d4b909.a9ac85e58307d0375fe4.js

650 ms

_app-23380992b38ee9d2bad5.js

_app-23380992b38ee9d2bad5.js

666 ms

cb1608f2.6a856b0862fe29aace67.js

cb1608f2.6a856b0862fe29aace67.js

899 ms

index-9b15ade211b1ba387537.js

index-9b15ade211b1ba387537.js

664 ms

_buildManifest.js

_buildManifest.js

720 ms

_ssgManifest.js

_ssgManifest.js

722 ms

v4-discover-hand_EN.jpg

v4-discover-hand_EN.jpg

40 ms

v4-search-hand_EN.jpg

v4-search-hand_EN.jpg

46 ms

v4-save-hand_EN.jpg

v4-save-hand_EN.jpg

39 ms

proximabold.woff

proximabold.woff

666 ms

proximaextrabold.woff

proximaextrabold.woff

514 ms

proximasemi.woff

proximasemi.woff

581 ms

Peopleicons.woff

Peopleicons.woff

612 ms

config.js

config.js

4 ms

Accessibility Review

get.peoople.co accessibility score

78

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

Document doesn't have a <title> element

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

get.peoople.co 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

SEO Factors

get.peoople.co SEO score

58

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

get.peoople.co

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