Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

elocal.co.nz

elocal magazine - Voice Media

Page Load Speed

6.5 sec in total

First Response

434 ms

Resources Loaded

5.7 sec

Page Rendered

328 ms

elocal.co.nz screenshot

About Website

Visit elocal.co.nz now to see the best up-to-date Elocal content and also check out these interesting facts you probably never knew about elocal.co.nz

Proudly Independent, Focused on New Zealand and International Based Articles Established in 2004, elocal is a proudly independent, NZ-owned and ope...

Visit elocal.co.nz

Key Findings

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

Performance Metrics

elocal.co.nz performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

elocal.co.nz

434 ms

elocal.co.nz

859 ms

www.elocal.co.nz

962 ms

277

504 ms

analytics.js

20 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 75% of them (40 requests) were addressed to the original Elocal.co.nz, 9% (5 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Elocal.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.3 kB (6%)

Content Size

2.4 MB

After Optimization

2.3 MB

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

HTML Optimization

-78%

Potential reduce by 53.1 kB

  • Original 68.1 kB
  • After minification 59.1 kB
  • After compression 15.0 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 9.0 kB, which is 13% 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 53.1 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 67.7 kB

  • Original 2.3 MB
  • After minification 2.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. Elocal images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 23.4 kB

  • Original 53.6 kB
  • After minification 53.5 kB
  • After compression 30.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 23.4 kB or 44% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (19%)

Requests Now

43

After Optimization

35

The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elocal. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

elocal.co.nz accessibility score

61

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

elocal.co.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

elocal.co.nz SEO score

77

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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