Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

perto.com

Your worldwide event portal - explore the events that suit you best

Page Load Speed

2.4 sec in total

First Response

481 ms

Resources Loaded

1.8 sec

Page Rendered

133 ms

About Website

Welcome to perto.com homepage info - get ready to check Perto best content for Germany right away, or after learning these important things about perto.com

This ultimate guide to the best things to do around you ✔ find your next events and get your tickets

Visit perto.com

Key Findings

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

Performance Metrics

perto.com performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value3.5 s

89/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

en.perto.com

481 ms

merged-902f3510014eb1139ced4d30d5e24e7e.css

49 ms

merged-f67982515b27fe2f305bad568efa27d9.js

75 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

37 ms

share-variant.svg

22 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Perto.com, 17% (2 requests) were made to Cdn.perto.com and 8% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (665 ms) relates to the external source Perto.page.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.7 kB (36%)

Content Size

280.7 kB

After Optimization

180.1 kB

In fact, the total size of Perto.com main page is 280.7 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 146.1 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 100.6 kB

  • Original 127.7 kB
  • After minification 127.7 kB
  • After compression 27.1 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 100.6 kB or 79% of the original size.

JavaScript Optimization

-0%

Potential reduce by 76 B

  • Original 146.1 kB
  • After minification 146.1 kB
  • After compression 146.0 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

-0%

Potential reduce by 0 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 7.0 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. Perto.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

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

Accessibility Review

perto.com accessibility score

97

Accessibility Issues

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

perto.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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