2.3 sec in total
460 ms
1.6 sec
283 ms
Welcome to efes.co.nz homepage info - get ready to check EFES best content for New Zealand right away, or after learning these important things about efes.co.nz
EFES Beer - New Zealand's exclusive agent
Visit efes.co.nzWe analyzed Efes.co.nz page load time and found that the first response time was 460 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
efes.co.nz performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value10.2 s
0/100
25%
Value14.5 s
1/100
10%
Value670 ms
45/100
30%
Value0.472
18/100
15%
Value8.5 s
38/100
10%
460 ms
22 ms
86 ms
71 ms
49 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 54% of them (52 requests) were addressed to the original Efes.co.nz, 25% (24 requests) were made to Maps.googleapis.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (460 ms) belongs to the original domain Efes.co.nz.
Page size can be reduced by 1.1 MB (36%)
3.1 MB
2.0 MB
In fact, the total size of Efes.co.nz main page is 3.1 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 39.2 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 39.2 kB or 82% of the original size.
Potential reduce by 53.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. EFES images are well optimized though.
Potential reduce by 665.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 665.0 kB or 69% of the original size.
Potential reduce by 371.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. Efes.co.nz needs all CSS files to be minified and compressed as it can save up to 371.7 kB or 86% of the original size.
Number of requests can be reduced by 53 (60%)
89
36
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EFES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
efes.co.nz
460 ms
analytics.js
22 ms
bootstrap.css
86 ms
k2.css
71 ms
system.css
49 ms
template.css
126 ms
megamenu.css
57 ms
off-canvas.css
58 ms
font-awesome.min.css
98 ms
custom.css
77 ms
animate.min.css
98 ms
style.css
98 ms
allvideoshare.css
100 ms
allvideoshareupdate.css
104 ms
style.css
105 ms
mootools-core.js
145 ms
core.js
114 ms
jquery.min.js
167 ms
jquery-noconflict.js
118 ms
jquery-migrate.min.js
132 ms
k2.js
136 ms
caption.js
132 ms
bootstrap.js
158 ms
jquery.tap.min.js
152 ms
off-canvas.js
158 ms
script.js
159 ms
menu.js
163 ms
modernizr.custom.61760.js
182 ms
bootstrap-datepicker.js
192 ms
headroom.min.js
190 ms
jquery.masonry.min.js
181 ms
retina-1.1.0.min.js
184 ms
script.js
200 ms
nav-collapse.js
202 ms
js
63 ms
script.js
287 ms
wowslider.js
211 ms
script.js
209 ms
collect
26 ms
system.css
180 ms
css
24 ms
css
37 ms
font-awesome.css
151 ms
EFES-logo.png
75 ms
slide1.jpg
117 ms
slide2.jpg
203 ms
slide3.jpg
118 ms
efes.co.nz
350 ms
Efes_Pilsener1.png
120 ms
Efes_Pilsener2.png
75 ms
Efes_zero1.png
121 ms
Efes_zero2.png
121 ms
FreeDelivery.JPG
202 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
22 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
23 ms
arrows.png
171 ms
lines_1.png
171 ms
icon_social_1.png
171 ms
common.js
10 ms
map.js
22 ms
util.js
49 ms
marker.js
48 ms
geometry.js
47 ms
directions.js
48 ms
lines.png
154 ms
onion.js
16 ms
openhand_8_8.cur
91 ms
ViewportInfoService.GetViewportInfo
103 ms
stats.js
50 ms
controls.js
46 ms
infowindow.js
41 ms
css
99 ms
transparent.png
27 ms
google4.png
41 ms
mapcnt6.png
66 ms
sv5.png
66 ms
tmapctrl.png
51 ms
tmapctrl4.png
65 ms
imgs8.png
70 ms
spotlight-poi.png
82 ms
vt
76 ms
vt
72 ms
vt
70 ms
vt
61 ms
vt
63 ms
vt
60 ms
vt
93 ms
vt
97 ms
vt
102 ms
vt
122 ms
vt
144 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
50 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
59 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
66 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
66 ms
AuthenticationService.Authenticate
51 ms
efes.co.nz accessibility score
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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
efes.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
efes.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efes.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 Efes.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.
efes.co.nz
Open Graph description is not detected on the main page of EFES. 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: