Tools & Wizards About Us
seeka.co.nz screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

seeka.co.nz

Seeka | Produce Packhouse & Coolstore Facilities

Page Load Speed

5.3 sec in total

First Response

46 ms

Resources Loaded

5.2 sec

Page Rendered

101 ms

seeka.co.nz screenshot

About Website

Click here to check amazing Seeka content for New Zealand. Otherwise, check out these important facts you probably never knew about seeka.co.nz

Seeka provide a premier orchard to packhouse and produce to market service for growing, handling and storing fruit for prime producers of NZ's finest produce.

Visit seeka.co.nz

Key Findings

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

Performance Metrics

seeka.co.nz performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.114

86/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

seeka.co.nz

46 ms

seeka.co.nz

683 ms

www.seeka.co.nz

1031 ms

js

81 ms

hwffek1l89

56 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 47% of them (26 requests) were addressed to the original Seeka.co.nz, 20% (11 requests) were made to Fonts.gstatic.com and 11% (6 requests) were made to Cmp.inmobi.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Seeka.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.5 kB (14%)

Content Size

269.5 kB

After Optimization

232.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Seeka.co.nz main page is 269.5 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. 45% of websites need less resources to load. Javascripts take 140.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 32.1 kB

  • Original 38.6 kB
  • After minification 38.4 kB
  • After compression 6.5 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 32.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 61.4 kB
  • After minification 61.4 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. Seeka images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 579 B

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

-14%

Potential reduce by 3.9 kB

  • Original 28.6 kB
  • After minification 28.6 kB
  • After compression 24.7 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. Seeka.co.nz needs all CSS files to be minified and compressed as it can save up to 3.9 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (66%)

Requests Now

41

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seeka.co.nz

seeka.co.nz

46 ms

seeka.co.nz

seeka.co.nz

683 ms

www.seeka.co.nz

www.seeka.co.nz

1031 ms

js

js

81 ms

hwffek1l89

hwffek1l89

56 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

676 ms

jquery.fancybox-1.3.0.pack.js

jquery.fancybox-1.3.0.pack.js

705 ms

ui.dialog.css

ui.dialog.css

715 ms

jquery.fancybox-1.3.0.css

jquery.fancybox-1.3.0.css

696 ms

slimmenu.min.css

slimmenu.min.css

718 ms

jquery.slimmenu.min.js

jquery.slimmenu.min.js

705 ms

2016_seeka.css

2016_seeka.css

1355 ms

css

css

51 ms

css

css

67 ms

privacy.js

privacy.js

1386 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

76 ms

clarity.js

clarity.js

7 ms

fbevents.js

fbevents.js

89 ms

gtm.js

gtm.js

77 ms

gtm.js

gtm.js

89 ms

logo.jpg

logo.jpg

668 ms

searchIcon.png

searchIcon.png

656 ms

menuHover.png

menuHover.png

729 ms

i891_0_0

i891_0_0

729 ms

homeArrow.jpg

homeArrow.jpg

728 ms

i827_0_0

i827_0_0

1094 ms

seekaIcon.png

seekaIcon.png

1296 ms

i1028_0_0

i1028_0_0

1561 ms

homeCallout.jpg

homeCallout.jpg

1320 ms

i864_0_0

i864_0_0

1756 ms

headingArrowWhite.png

headingArrowWhite.png

1378 ms

footer_bg.jpg

footer_bg.jpg

1771 ms

facebookIcon.png

facebookIcon.png

1983 ms

youtubeIcon.png

youtubeIcon.png

1979 ms

ga.js

ga.js

84 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

58 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

77 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

85 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

88 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

88 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

87 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

87 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

100 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

99 ms

__utm.gif

__utm.gif

26 ms

choice.js

choice.js

416 ms

cmp2-polyfilled.js

cmp2-polyfilled.js

3 ms

geoip

geoip

2 ms

cmp-list.json

cmp-list.json

1 ms

cmp2ui-en.js

cmp2ui-en.js

6 ms

vendor-list-trimmed-v1.json

vendor-list-trimmed-v1.json

16 ms

main.js

main.js

9 ms

c.gif

c.gif

9 ms

Accessibility Review

seeka.co.nz accessibility score

86

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.

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

seeka.co.nz best practices score

50

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

seeka.co.nz SEO score

83

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

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

seeka.co.nz

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