Tools & Wizards About Us
phoneforelderly.co.za screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    51% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

phoneforelderly.co.za

Phone for Elderly South Africa – Big Button Phones For Seniors

Page Load Speed

6.2 sec in total

First Response

1.4 sec

Resources Loaded

4.3 sec

Page Rendered

462 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

As mobile phone technology increases they become packed with more and more functionality and smaller buttons or no buttons. This makes it really difficult for

Visit phoneforelderly.co.za

Key Findings

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

Performance Metrics

phoneforelderly.co.za performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.15

76/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.phoneforelderly.co.za

1416 ms

wp-emoji-release.min.js

65 ms

style.min.css

179 ms

mediaelementplayer-legacy.min.css

255 ms

wp-mediaelement.min.css

273 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 65% of them (52 requests) were addressed to the original Phoneforelderly.co.za, 6% (5 requests) were made to Google-analytics.com and 6% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Phoneforelderly.co.za.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.0 kB (17%)

Content Size

375.6 kB

After Optimization

310.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 53.6 kB

  • Original 68.8 kB
  • After minification 63.3 kB
  • After compression 15.2 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 53.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 2.1 kB

  • Original 106.1 kB
  • After minification 104.0 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. Phone For Elderly images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.3 kB

  • Original 102.7 kB
  • After minification 102.7 kB
  • After compression 100.4 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

-7%

Potential reduce by 7.0 kB

  • Original 98.0 kB
  • After minification 97.9 kB
  • After compression 91.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. Phoneforelderly.co.za has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 56 (77%)

Requests Now

73

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 73 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 37 to 1 for JavaScripts and from 21 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

1416 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

65 ms

style.min.css

style.min.css

179 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

255 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

273 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

275 ms

wc-blocks-style.css

wc-blocks-style.css

296 ms

form_style.css

form_style.css

251 ms

woocommerce-layout.css

woocommerce-layout.css

269 ms

woocommerce.css

woocommerce.css

335 ms

font-awesome.min.css

font-awesome.min.css

106 ms

owl.carousel.css

owl.carousel.css

325 ms

owl.transitions.css

owl.transitions.css

339 ms

colorbox.css

colorbox.css

340 ms

animate.css

animate.css

325 ms

tx-style.css

tx-style.css

358 ms

superfish.css

superfish.css

366 ms

css

css

201 ms

style.css

style.css

353 ms

responsive.css

responsive.css

355 ms

local-ryviu.css

local-ryviu.css

350 ms

jetpack.css

jetpack.css

397 ms

jquery.min.js

jquery.min.js

453 ms

jquery-migrate.min.js

jquery-migrate.min.js

433 ms

js.cookie.min.js

js.cookie.min.js

434 ms

gtm4wp-woocommerce-enhanced.js

gtm4wp-woocommerce-enhanced.js

430 ms

s-202240.js

s-202240.js

197 ms

hoverIntent.min.js

hoverIntent.min.js

434 ms

superfish.js

superfish.js

483 ms

custom.js

custom.js

483 ms

jquery.bxslider.js

jquery.bxslider.js

487 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

485 ms

public.js

public.js

510 ms

js

js

268 ms

1.js

1.js

207 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

503 ms

woocommerce.min.js

woocommerce.min.js

504 ms

cart-fragments.min.js

cart-fragments.min.js

507 ms

imagesloaded.min.js

imagesloaded.min.js

530 ms

masonry.min.js

masonry.min.js

530 ms

jquery.masonry.min.js

jquery.masonry.min.js

552 ms

app.js

app.js

298 ms

e-202240.js

e-202240.js

185 ms

owl.carousel.min.js

owl.carousel.min.js

857 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

840 ms

jquery.inview.min.js

jquery.inview.min.js

721 ms

tx-script.js

tx-script.js

636 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

633 ms

navigation.js

navigation.js

711 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

708 ms

local-ryviu.js

local-ryviu.js

708 ms

gtm.js

gtm.js

53 ms

analytics.js

analytics.js

50 ms

Front-slider.jpg

Front-slider.jpg

441 ms

SOS-slider.jpg

SOS-slider.jpg

442 ms

Easy-to-hold-slider.jpg

Easy-to-hold-slider.jpg

439 ms

Cradle-charger-slider.jpg

Cradle-charger-slider.jpg

656 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

407 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

531 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

622 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

619 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

621 ms

slider-shadow.png

slider-shadow.png

607 ms

linkid.js

linkid.js

304 ms

ec.js

ec.js

305 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

276 ms

conversion_async.js

conversion_async.js

267 ms

client.json

client.json

329 ms

client.json

client.json

349 ms

collect

collect

221 ms

collect

collect

72 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

149 ms

prev-next.png

prev-next.png

93 ms

collect

collect

29 ms

119 ms

overlay.png

overlay.png

90 ms

ga-audiences

ga-audiences

107 ms

ajax

ajax

291 ms

205.svg

205.svg

83 ms

18 ms

Accessibility Review

phoneforelderly.co.za accessibility score

75

Accessibility Issues

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.

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 IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

SEO Factors

phoneforelderly.co.za SEO score

79

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 data is detected on the main page of Phone For Elderly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: