Tools & Wizards About Us

Report Summary

  • 2

    Performance

    Renders faster than
    20% 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

  • 80

    SEO

    Google-friendlier than
    42% of websites

papaya.com.au

Furniture & Homewares Online in Sydney & Melbourne, Australia - Papaya

Page Load Speed

16.8 sec in total

First Response

473 ms

Resources Loaded

16.1 sec

Page Rendered

317 ms

About Website

Click here to check amazing Papaya content for Australia. Otherwise, check out these important facts you probably never knew about papaya.com.au

Est. in 1996 - the Papaya brand is a synergy between the unspoiled beauty of raw materials & the understated clarity of contemporary design. Shop online now.

Visit papaya.com.au

Key Findings

We analyzed Papaya.com.au page load time and found that the first response time was 473 ms and then it took 16.4 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

papaya.com.au performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value24.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,940 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.733

6/100

15%

TTI (Time to Interactive)

Value35.8 s

0/100

10%

Network Requests Diagram

papaya.com.au

473 ms

www.papaya.com.au

1058 ms

67efdd265615dcb0f1b72ce70501ff76.min.css

622 ms

styles-l.min.css

809 ms

f003c37ca8f4d2efafd4c03cf35f89e1.min.js

824 ms

Our browser made a total of 216 requests to load all elements on the main page. We found that 85% of them (183 requests) were addressed to the original Papaya.com.au, 4% (8 requests) were made to Static.klaviyo.com and 2% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Papaya.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 488.7 kB (10%)

Content Size

5.1 MB

After Optimization

4.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Papaya.com.au main page is 5.1 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 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 277.9 kB

  • Original 316.9 kB
  • After minification 312.9 kB
  • After compression 39.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 277.9 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 100.8 kB

  • Original 4.1 MB
  • After minification 4.0 MB

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. Papaya images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 110.0 kB

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

CSS Optimization

-0%

Potential reduce by 39 B

  • Original 199.6 kB
  • After minification 199.6 kB
  • After compression 199.5 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. Papaya.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 156 (76%)

Requests Now

204

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

papaya.com.au 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

[role]s do not have all required [aria-*] attributes

High

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

papaya.com.au 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

Displays images with incorrect aspect ratio

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

papaya.com.au SEO score

80

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Papaya.com.au 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 Papaya.com.au 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 description is not detected on the main page of Papaya. 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: