813 ms in total
230 ms
436 ms
147 ms
Click here to check amazing Drupal content. Otherwise, check out these important facts you probably never knew about drupal.nz
NZ's primary website for Drupal community events, showcases, case studies, contractors, companies and more. Drupal NZ is built and maintained by the Wellington Drupal Meetup Community.
Visit drupal.nzWe analyzed Drupal.nz page load time and found that the first response time was 230 ms and then it took 583 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
drupal.nz performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value4.7 s
31/100
25%
Value2.2 s
99/100
10%
Value230 ms
87/100
30%
Value0
100/100
15%
Value4.8 s
79/100
10%
230 ms
91 ms
78 ms
13 ms
18 ms
Our browser made a total of 23 requests to load all elements on the main page. We found that 74% of them (17 requests) were addressed to the original Drupal.nz, 17% (4 requests) were made to Fonts.gstatic.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (230 ms) belongs to the original domain Drupal.nz.
Page size can be reduced by 63.3 kB (10%)
638.9 kB
575.6 kB
In fact, the total size of Drupal.nz main page is 638.9 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. 30% of websites need less resources to load. Images take 530.9 kB which makes up the majority of the site volume.
Potential reduce by 17.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 2.4 kB, which is 11% 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 17.9 kB or 78% of the original size.
Potential reduce by 31.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. Drupal images are well optimized though.
Potential reduce by 11.6 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 11.6 kB or 16% of the original size.
Potential reduce by 2.8 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. Drupal.nz needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 22% of the original size.
We found no issues to fix!
17
17
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drupal. According to our analytics all requests are already optimized.
drupal.nz
230 ms
drupal.nz
91 ms
js
78 ms
css_-Gcm8DJO69_TsagFWkMGHj-HSx2sCSahglVn8BwRlBA.css
13 ms
css_L67PaK1Q4Q9NEd0WLfZwHcWtuMX0qpIOEqdTmEYqcVk.css
18 ms
js_esoIG_PUAI5P6805Ru7CyhTpPAoI4XwIq8RE8ndIPdM.js
27 ms
logo.svg
25 ms
menu.svg
28 ms
groupinembassy.jpg
35 ms
Screenshot_2020-09-25%20Your%20complete%20guide%20to%20NZ%20Election%202020%20%E2%80%94%20Policy%282%29.png
32 ms
AkoScreenshot4.png
31 ms
app.letscollaborate.co_.nz_user_51.png
34 ms
www.aim_.com_.au_%20%284%29%20%281%29.png
39 ms
meetup.svg
38 ms
drupalcon.svg
40 ms
xequals-white.svg
45 ms
logo-pantheon--white.svg
42 ms
css
36 ms
img-header.svg
26 ms
4iCs6KVjbNBYlgoKfw7z.ttf
28 ms
4iCv6KVjbNBYlgoCjC3jsGyI.ttf
33 ms
4iCv6KVjbNBYlgoC1CzjsGyI.ttf
40 ms
4iCv6KVjbNBYlgoCxCvjsGyI.ttf
37 ms
drupal.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
drupal.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
drupal.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drupal.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 Drupal.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.
drupal.nz
Open Graph description is not detected on the main page of Drupal. 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: