4.1 sec in total
46 ms
3.4 sec
681 ms
Welcome to databook.co.nz homepage info - get ready to check Data Book best content for New Zealand right away, or after learning these important things about databook.co.nz
Welcome New Zealand’s comprehensive Screen Production industry directory. Published since 1988 and online since 2000.
Visit databook.co.nzWe analyzed Databook.co.nz page load time and found that the first response time was 46 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
databook.co.nz performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value6.8 s
7/100
25%
Value7.0 s
32/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value10.1 s
26/100
10%
46 ms
1293 ms
11 ms
31 ms
856 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 33% of them (26 requests) were addressed to the original Databook.co.nz, 47% (37 requests) were made to Databooknz.s3.amazonaws.com and 10% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Databook.co.nz.
Page size can be reduced by 152.8 kB (1%)
21.8 MB
21.7 MB
In fact, the total size of Databook.co.nz main page is 21.8 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. Only a small number of websites need less resources to load. Images take 21.3 MB which makes up the majority of the site volume.
Potential reduce by 111.3 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 111.3 kB or 87% of the original size.
Potential reduce by 41.3 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. Data Book images are well optimized though.
Potential reduce by 153 B
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.
Potential reduce by 0 B
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. Databook.co.nz has all CSS files already compressed.
Number of requests can be reduced by 6 (9%)
69
63
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Book. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
databook.co.nz
46 ms
www.databook.co.nz
1293 ms
application-98ec10669a0c99a8681dbe4d68166438.css
11 ms
application-250e0dd53d2e3db24f0523c460b95f7b.js
31 ms
spcjs.php
856 ms
ybd6sgm.js
85 ms
spc.php
220 ms
fl.js
422 ms
Hero-Animals.gif
428 ms
logo-243dd409610f4535af83639e74f47502.svg
274 ms
Slider_5.jpg
497 ms
IMG_4892.jpg
546 ms
Slider_4.jpg
599 ms
IMG_20161115_203352.jpg
471 ms
Slider_3.jpg
425 ms
IMG_20161115_203312.jpg
586 ms
Auckland-Actors-Voices.gif
473 ms
logo.jpg
475 ms
HD-Shaded.png
479 ms
The_Workroom_Logo_-_Primary_Slate_Bg-01__6_.png
491 ms
JPRO_Experience_AVC_Blue.png
510 ms
Social_Media_Icon.png
571 ms
Belmont_logo_for_invoices.png
537 ms
BONZ_BESTofNZ_black_rev.png
556 ms
StorageDepot.jpg
563 ms
logo_round_name__1_.png
609 ms
screen-wgtn-16.9-positive-rgb.jpg
578 ms
Logotype_Large.png
638 ms
cinematographer.png
604 ms
Screenshot_2022-08-08_at_14.26.15.jpeg
663 ms
PIRANHA_VOICE_AGENCY.jpg
631 ms
DVANZ_Logo_2022.png
632 ms
FilmRadios.jpg
647 ms
Xtreme.jpg
639 ms
Belmont_Studio_Logo.png
669 ms
LOGO_Brustics_landscape_products_naturally_-_Black_no_border_png.png
669 ms
Wireless_Rentals_-_Logo-3.jpg
701 ms
NZFC_Primary_Block_with_Reo.png
706 ms
Solo_self-employed-accounting-software.png
705 ms
logo.jpg
693 ms
DD.jpg
693 ms
430C5E63-2DFE-4168-8305-60021DBA54E3.jpeg
747 ms
APEX_Insurance_1clr_nobox.jpg
722 ms
AANZ-Logo-Reverse.jpg
765 ms
Pitt__Moore__Logo_.jpg
743 ms
wave-1fe575b6b4cdc954836bdbc9d7ab3035.svg
279 ms
search-icon-2724d8d51bf92970faf6cea028b95149.png
283 ms
categories-icon-54fee6b299d558f6bec5fc80801ee2a7.png
317 ms
cities-icon-1d393c8fc10910185c73462a720eb203.png
316 ms
location-icon-01549fc025df2b2dadff01fa74414b0f.png
315 ms
country-icon-d1bfb48ec1702458918665692aa72f98.png
315 ms
icon-go-e8bf67913dd9f8e5a5bf51efe2449ba8.svg
316 ms
art--props-30f493bc354decf91f164ed42bcf5f64.svg
343 ms
camera-e9f843c4806e64b521c9bc9465dd7492.svg
346 ms
casting-e57d7c4231c9f95e905fbd49eebeaf8e.svg
352 ms
direction-02c13ad365e5d1c9c21d3bf4bd48e94e.svg
349 ms
hire-b48de8441eadb99670a6ba6b881fc0f8.svg
351 ms
lighting-5fe595bcfe15964f6afed4eaa6179c5c.svg
347 ms
locations-dcab97daf4ac83d64b03b06e77a928b4.svg
349 ms
organisations-54442df054f03abb78369ebc55c7768e.svg
352 ms
post-production-012a13df5de1427b9cec5553e316e62e.svg
353 ms
pro-support-9ab6e31490c138ca7a541b47357e1f3b.svg
354 ms
production-7566a72fdd7fbbcee6c3cb4f5331a867.svg
414 ms
sound--audio-e5872c4cac0cbd72643318779009fb26.svg
412 ms
icon-location-hm-486712af35d4f0ffd8c99ce3d16b7190.svg
415 ms
icon-category-tag-hm-980cb241bb904a69b5c09d619192d8ca.svg
412 ms
analytics.js
343 ms
gtm.js
415 ms
d
13 ms
d
70 ms
d
43 ms
d
70 ms
d
70 ms
d
70 ms
d
71 ms
collect
57 ms
KKM_logo.png
312 ms
p.gif
38 ms
databook.co.nz accessibility score
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
databook.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
databook.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Databook.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 Databook.co.nz main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
databook.co.nz
Open Graph description is not detected on the main page of Data Book. 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: