Tools & Wizards About Us
planyo.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

planyo.com

Online reservation system & booking software Planyo

Page Load Speed

38.3 sec in total

First Response

643 ms

Resources Loaded

20.1 sec

Page Rendered

17.6 sec

planyo.com screenshot

About Website

Visit planyo.com now to see the best up-to-date Planyo content for United States and also check out these interesting facts you probably never knew about planyo.com

Planyo is a flexible online reservation system / booking software for any business which needs scheduling and managing their bookings.

Visit planyo.com

Key Findings

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

Performance Metrics

planyo.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value400 ms

68/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

planyo.com

643 ms

www.planyo.com

594 ms

css

1326 ms

bootstrap.min.css

1473 ms

planyo-homepage-scheme.css

823 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 18% of them (8 requests) were addressed to the original Planyo.com, 18% (8 requests) were made to S3.amazonaws.com and 11% (5 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 701.0 kB (37%)

Content Size

1.9 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Planyo.com main page is 1.9 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. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.8 kB

  • Original 43.4 kB
  • After minification 41.1 kB
  • After compression 10.6 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 32.8 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 35.6 kB

  • Original 1.0 MB
  • After minification 975.2 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. Planyo images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 286.9 kB

  • Original 455.4 kB
  • After minification 455.4 kB
  • After compression 168.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 286.9 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 345.7 kB

  • Original 407.2 kB
  • After minification 404.1 kB
  • After compression 61.6 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. Planyo.com needs all CSS files to be minified and compressed as it can save up to 345.7 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

36

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

planyo.com

planyo.com

643 ms

www.planyo.com

www.planyo.com

594 ms

css

css

1326 ms

bootstrap.min.css

bootstrap.min.css

1473 ms

planyo-homepage-scheme.css

planyo-homepage-scheme.css

823 ms

font-awesome.min.css

font-awesome.min.css

825 ms

bootstrap-glyphicons.css

bootstrap-glyphicons.css

1226 ms

jquery.min.js

jquery.min.js

1471 ms

bootstrap.min.js

bootstrap.min.js

1388 ms

logo.png

logo.png

1022 ms

css

css

743 ms

bcg01.jpg

bcg01.jpg

4544 ms

138867865

138867865

4040 ms

securimage_show.php

securimage_show.php

1856 ms

swissmadesoftware-logo.png

swissmadesoftware-logo.png

7294 ms

planyo_icons.jpg

planyo_icons.jpg

3775 ms

planyo_responsive.jpg

planyo_responsive.jpg

3775 ms

planyo_extensions.jpg

planyo_extensions.jpg

3775 ms

planyo_reference.png

planyo_reference.png

3774 ms

ref_2883.jpg

ref_2883.jpg

3926 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

4307 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

7023 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

8290 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

8289 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

1934 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

5300 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1933 ms

analytics.js

analytics.js

924 ms

widgets.js

widgets.js

1885 ms

like.php

like.php

5098 ms

_Incapsula_Resource

_Incapsula_Resource

407 ms

player.js

player.js

6717 ms

player.css

player.css

6717 ms

ga.js

ga.js

5160 ms

vuid.min.js

vuid.min.js

6620 ms

_Incapsula_Resource

_Incapsula_Resource

2748 ms

collect

collect

2241 ms

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js

3486 ms

0zf7krTbbuX.js

0zf7krTbbuX.js

3301 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

3617 ms

__utm.gif

__utm.gif

358 ms

bcg02.jpg

bcg02.jpg

2841 ms

reel3dark.jpg

reel3dark.jpg

2851 ms

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

tweet_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html

919 ms

jot

jot

2675 ms

Accessibility Review

planyo.com accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

planyo.com best practices score

67

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

planyo.com SEO score

83

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

Image elements do not have [alt] attributes

High

Document uses plugins

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 Planyo.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 Planyo.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

planyo.com

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