Tools & Wizards About Us
purecafe.co.za screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

purecafe.co.za

Pure Café Pretoria | Conference Facility | Catering | ONLINE Store

Page Load Speed

3.1 sec in total

First Response

380 ms

Resources Loaded

2.6 sec

Page Rendered

80 ms

purecafe.co.za screenshot

About Website

Welcome to purecafe.co.za homepage info - get ready to check Pure Cafe best content right away, or after learning these important things about purecafe.co.za

Pure Café Colbyn, Speciality Coffee Shop, Breakfast, Lunch, Catering, Functions, Venue, Street Café, Conference Facility, Boardroom Facility, Pretoria, Cakes, Deli, Weddings, Live Events,

Visit purecafe.co.za

Key Findings

We analyzed Purecafe.co.za page load time and found that the first response time was 380 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

purecafe.co.za performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

51/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

www.purecafe.co.za

380 ms

minified.js

45 ms

focus-within-polyfill.js

44 ms

polyfill.min.js

98 ms

thunderbolt-commons.b70ee867.bundle.min.js

76 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Purecafe.co.za, 32% (13 requests) were made to Static.wixstatic.com and 29% (12 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 657.4 kB (59%)

Content Size

1.1 MB

After Optimization

448.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Purecafe.co.za main page is 1.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. 20% of websites need less resources to load. HTML takes 755.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 606.6 kB

  • Original 755.7 kB
  • After minification 753.9 kB
  • After compression 149.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 606.6 kB or 80% of the original size.

Image Optimization

-6%

Potential reduce by 2.6 kB

  • Original 45.3 kB
  • After minification 42.7 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. Pure Cafe images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 304.3 kB
  • After minification 304.3 kB
  • After compression 256.2 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.purecafe.co.za

www.purecafe.co.za

380 ms

minified.js

minified.js

45 ms

focus-within-polyfill.js

focus-within-polyfill.js

44 ms

polyfill.min.js

polyfill.min.js

98 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

76 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

80 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

75 ms

lodash.min.js

lodash.min.js

82 ms

react.production.min.js

react.production.min.js

82 ms

react-dom.production.min.js

react-dom.production.min.js

188 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

79 ms

pure%20white%20logo.png

pure%20white%20logo.png

355 ms

bundle.min.js

bundle.min.js

64 ms

pure%20white%20logo.png

pure%20white%20logo.png

283 ms

ee2c2a_bd4389f55bc1484d87b9e89ad6ff627f~mv2.jpg

ee2c2a_bd4389f55bc1484d87b9e89ad6ff627f~mv2.jpg

1218 ms

TUKS_Spaces_Pure_Cafe_17.jpg

TUKS_Spaces_Pure_Cafe_17.jpg

442 ms

Tuks_Pure_Cafe_14.jpg

Tuks_Pure_Cafe_14.jpg

329 ms

Tuks_Pure_Cafe_42.jpg

Tuks_Pure_Cafe_42.jpg

328 ms

TUKS_ConferenceRoom1_Pure_Cafe_03.jpg

TUKS_ConferenceRoom1_Pure_Cafe_03.jpg

605 ms

ee2c2a_5409d6bceef74c4d93c5ca0855487174~mv2.jpg

ee2c2a_5409d6bceef74c4d93c5ca0855487174~mv2.jpg

617 ms

ee2c2a_e36e56d61a36411d9ffc4a87cb4b7153~mv2.jpg

ee2c2a_e36e56d61a36411d9ffc4a87cb4b7153~mv2.jpg

580 ms

ee2c2a_7d6025fdb2cc4c18aaea889fb5a0e5a5~mv2.jpg

ee2c2a_7d6025fdb2cc4c18aaea889fb5a0e5a5~mv2.jpg

623 ms

ee2c2a_116dc91e88724e5eb4df72362a0e262f~mv2.jpg

ee2c2a_116dc91e88724e5eb4df72362a0e262f~mv2.jpg

906 ms

ee2c2a_50543da9593b468590de82153e99b03f~mv2.jpg

ee2c2a_50543da9593b468590de82153e99b03f~mv2.jpg

833 ms

ee2c2a_a4b4af1e68bd4fbe8813f55cde9514ed~mv2.jpg

ee2c2a_a4b4af1e68bd4fbe8813f55cde9514ed~mv2.jpg

848 ms

115 ms

115 ms

113 ms

113 ms

113 ms

111 ms

144 ms

150 ms

149 ms

141 ms

143 ms

137 ms

deprecation-en.v5.html

deprecation-en.v5.html

10 ms

bolt-performance

bolt-performance

13 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

5 ms

Accessibility Review

purecafe.co.za accessibility score

91

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

Buttons do not have an accessible 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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

purecafe.co.za 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

purecafe.co.za 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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Purecafe.co.za 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 Purecafe.co.za 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

purecafe.co.za

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