Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mycasecovers.co.nz

myCaseCovers New Zealand - Premium Mobile Device Cases & Covers for iPhone, iPad & Samsung Galaxy Tablets

Page Load Speed

3.9 sec in total

First Response

719 ms

Resources Loaded

2.9 sec

Page Rendered

359 ms

mycasecovers.co.nz screenshot

About Website

Welcome to mycasecovers.co.nz homepage info - get ready to check MyCaseCovers best content for New Zealand right away, or after learning these important things about mycasecovers.co.nz

Premium cases & covers for smart phones and tablets, including iPhone, iPad, Galaxy series. Low Price & Affordable Shipping Options.

Visit mycasecovers.co.nz

Key Findings

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

Performance Metrics

mycasecovers.co.nz performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

mycasecovers.co.nz

719 ms

theme-733662c0-ac81-013c-cda1-3222b985adef.css

106 ms

css

99 ms

modernizr-custom.js

98 ms

js

144 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Mycasecovers.co.nz, 55% (38 requests) were made to Cdn11.bigcommerce.com and 7% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn11.bigcommerce.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 414.4 kB (32%)

Content Size

1.3 MB

After Optimization

881.1 kB

In fact, the total size of Mycasecovers.co.nz main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 552.6 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 360.3 kB

  • Original 399.3 kB
  • After minification 310.8 kB
  • After compression 38.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. This page needs HTML code to be minified as it can gain 88.5 kB, which is 22% 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 360.3 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 467 B

  • Original 552.6 kB
  • After minification 552.1 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. MyCaseCovers images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 53.6 kB

  • Original 343.6 kB
  • After minification 343.6 kB
  • After compression 290.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 53.6 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (37%)

Requests Now

63

After Optimization

40

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

Accessibility Review

mycasecovers.co.nz accessibility score

75

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

High

ARIA IDs are not unique

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

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

Page has valid source maps

SEO Factors

mycasecovers.co.nz SEO score

92

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

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 Mycasecovers.co.nz 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 Mycasecovers.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

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