Tools & Wizards About Us
doro.co.nz screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

doro.co.nz

Doro phones - Best phone for old people, Doro easy phones, best phones for seniors

Page Load Speed

16.9 sec in total

First Response

7 sec

Resources Loaded

9.6 sec

Page Rendered

308 ms

doro.co.nz screenshot

About Website

Click here to check amazing Doro content. Otherwise, check out these important facts you probably never knew about doro.co.nz

Looking for a phone that's easy to use for you or your family members ? Doro makes life easier with it's fall alert system and durable phones.

Visit doro.co.nz

Key Findings

We analyzed Doro.co.nz page load time and found that the first response time was 7 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

doro.co.nz performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

58/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value1,990 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

doro.co.nz

7028 ms

542 ms

en-gb

343 ms

gtm.js

62 ms

main.min.css

210 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Doro.co.nz, 87% (39 requests) were made to Doro.com and 7% (3 requests) were made to Sdk.privacy-center.org. The less responsive or slowest element that took the longest time to load (7 sec) belongs to the original domain Doro.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 236.1 kB (16%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Doro.co.nz main page is 1.5 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. 50% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 117.5 kB

  • Original 138.3 kB
  • After minification 123.5 kB
  • After compression 20.8 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. This page needs HTML code to be minified as it can gain 14.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 117.5 kB or 85% of the original size.

Image Optimization

-6%

Potential reduce by 78.5 kB

  • Original 1.3 MB
  • After minification 1.2 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. Doro images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 12 B

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

CSS Optimization

-42%

Potential reduce by 40.1 kB

  • Original 95.0 kB
  • After minification 94.9 kB
  • After compression 55.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. Doro.co.nz needs all CSS files to be minified and compressed as it can save up to 40.1 kB or 42% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

doro.co.nz

doro.co.nz

7028 ms

542 ms

en-gb

en-gb

343 ms

gtm.js

gtm.js

62 ms

main.min.css

main.min.css

210 ms

ruxitagentjs_ICA2SVfqr_10167190521165248.js

ruxitagentjs_ICA2SVfqr_10167190521165248.js

540 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

14 ms

js

js

728 ms

jquery.yu2fvl.css

jquery.yu2fvl.css

210 ms

icon_cart_white_mobile.svg

icon_cart_white_mobile.svg

107 ms

icon_search_white.svg

icon_search_white.svg

106 ms

icon_cart_black.svg

icon_cart_black.svg

211 ms

icon_cart_hover.svg

icon_cart_hover.svg

213 ms

icon_search_black.svg

icon_search_black.svg

293 ms

icon_search_hover.svg

icon_search_hover.svg

316 ms

mobiles_phones_1200x500_23.jpg

mobiles_phones_1200x500_23.jpg

364 ms

tabletwatch_1200x500.jpg

tabletwatch_1200x500.jpg

448 ms

accessories_1200x500_2.jpg

accessories_1200x500_2.jpg

480 ms

eva-198x145.png

eva-198x145.png

761 ms

kerstin-and-louise_banner-tb.jpg

kerstin-and-louise_banner-tb.jpg

479 ms

search-glass.svg

search-glass.svg

423 ms

search-clear.svg

search-clear.svg

467 ms

hero-image_maggan_1200.jpg

hero-image_maggan_1200.jpg

845 ms

hero-image_maggan_768.jpg

hero-image_maggan_768.jpg

674 ms

teaser-lazyload.png

teaser-lazyload.png

621 ms

teaser-mobile-lazyload.png

teaser-mobile-lazyload.png

622 ms

banner_fullbredd.jpg

banner_fullbredd.jpg

858 ms

banner_jean-luc_mobil.jpg

banner_jean-luc_mobil.jpg

895 ms

ikon_pin.png

ikon_pin.png

714 ms

ikon_headset.png

ikon_headset.png

774 ms

path-52.png

path-52.png

804 ms

group-59.png

group-59.png

869 ms

twitter-logo.png

twitter-logo.png

884 ms

in-white-59px-r.png

in-white-59px-r.png

914 ms

instagram-logo-png-background-image.png

instagram-logo-png-background-image.png

956 ms

loader.js

loader.js

491 ms

symbol_arrow_white_down.svg

symbol_arrow_white_down.svg

955 ms

hero-image_maggan_2560.jpg

hero-image_maggan_2560.jpg

1088 ms

quotationmark_white.svg

quotationmark_white.svg

980 ms

BrandonText-Regular.otf

BrandonText-Regular.otf

941 ms

BrandonText-Bold.otf

BrandonText-Bold.otf

1063 ms

BrandonText-Medium.otf

BrandonText-Medium.otf

1003 ms

sdk.ca54c4e95073cc7d42f19c3869a37882ee5f25dd.js

sdk.ca54c4e95073cc7d42f19c3869a37882ee5f25dd.js

5 ms

ui-gdpr-en-web.ca54c4e95073cc7d42f19c3869a37882ee5f25dd.js

ui-gdpr-en-web.ca54c4e95073cc7d42f19c3869a37882ee5f25dd.js

6 ms

logo_doro.svg

logo_doro.svg

357 ms

Accessibility Review

doro.co.nz accessibility score

69

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

doro.co.nz best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

doro.co.nz SEO score

76

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doro.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Doro.co.nz 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

doro.co.nz

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