Tools & Wizards About Us
phoneforelderly.co.za screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

phoneforelderly.co.za

Phone for Elderly South Africa – Big Button Phones For Seniors

Page Load Speed

4.1 sec in total

First Response

1.2 sec

Resources Loaded

2.7 sec

Page Rendered

111 ms

phoneforelderly.co.za screenshot

About Website

Welcome to phoneforelderly.co.za homepage info - get ready to check Phone For Elderly best content right away, or after learning these important things about phoneforelderly.co.za

Visit phoneforelderly.co.za

Key Findings

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

Performance Metrics

phoneforelderly.co.za performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

www.phoneforelderly.co.za

1216 ms

form_style.css

25 ms

local-ryviu.css

30 ms

flatsome.css

34 ms

flatsome-shop.css

45 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Phoneforelderly.co.za, 4% (2 requests) were made to Stats.wp.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Phoneforelderly.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.4 kB (24%)

Content Size

408.8 kB

After Optimization

310.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Phoneforelderly.co.za main page is 408.8 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. 50% of websites need less resources to load. Images take 254.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 71.4 kB

  • Original 93.3 kB
  • After minification 91.3 kB
  • After compression 21.9 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 71.4 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 26.9 kB

  • Original 254.1 kB
  • After minification 227.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. Obviously, Phone For Elderly needs image optimization as it can save up to 26.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 58 B

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

Requests Breakdown

Number of requests can be reduced by 38 (83%)

Requests Now

46

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.phoneforelderly.co.za

www.phoneforelderly.co.za

1216 ms

form_style.css

form_style.css

25 ms

local-ryviu.css

local-ryviu.css

30 ms

flatsome.css

flatsome.css

34 ms

flatsome-shop.css

flatsome-shop.css

45 ms

style.css

style.css

27 ms

jquery.min.js

jquery.min.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

58 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

58 ms

js.cookie.min.js

js.cookie.min.js

66 ms

woocommerce.min.js

woocommerce.min.js

66 ms

s-202435.js

s-202435.js

20 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

176 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

171 ms

public.js

public.js

250 ms

email-decode.min.js

email-decode.min.js

10 ms

wc-blocks.css

wc-blocks.css

19 ms

js

js

70 ms

hooks.min.js

hooks.min.js

18 ms

i18n.min.js

i18n.min.js

25 ms

main.js

main.js

33 ms

sourcebuster.min.js

sourcebuster.min.js

32 ms

order-attribution.min.js

order-attribution.min.js

37 ms

flatsome-live-search.js

flatsome-live-search.js

46 ms

underscore.min.js

underscore.min.js

47 ms

wp-util.min.js

wp-util.min.js

47 ms

woo-feed-facebook-pixel.min.js

woo-feed-facebook-pixel.min.js

59 ms

local-ryviu.js

local-ryviu.js

63 ms

app.js

app.js

93 ms

wp-polyfill.min.js

wp-polyfill.min.js

62 ms

hoverIntent.min.js

hoverIntent.min.js

74 ms

flatsome.js

flatsome.js

76 ms

woocommerce.js

woocommerce.js

76 ms

e-202435.js

e-202435.js

7 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

86 ms

zxcvbn-async.min.js

zxcvbn-async.min.js

89 ms

password-strength-meter.min.js

password-strength-meter.min.js

88 ms

password-strength-meter.min.js

password-strength-meter.min.js

98 ms

fbevents.js

fbevents.js

93 ms

cropped-cell2.png

cropped-cell2.png

83 ms

Uniwa-V1000-single-247x296.png

Uniwa-V1000-single-247x296.png

83 ms

Uniwa-V1000-Front-and-Back-247x296.png

Uniwa-V1000-Front-and-Back-247x296.png

83 ms

Photo-contact-calling-247x296.png

Photo-contact-calling-247x296.png

82 ms

Simple-menu-options-247x296.png

Simple-menu-options-247x296.png

83 ms

SOS-Wrist-Band-1-247x296.png

SOS-Wrist-Band-1-247x296.png

82 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

39 ms

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff

38 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

39 ms

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff

38 ms

fl-icons.ttf

fl-icons.ttf

39 ms

chunk.countup.js

chunk.countup.js

52 ms

zxcvbn.min.js

zxcvbn.min.js

59 ms

Accessibility Review

phoneforelderly.co.za accessibility score

95

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-hidden="true"] elements contain focusable descendents

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.

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

phoneforelderly.co.za SEO score

93

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

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

phoneforelderly.co.za

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