4.8 sec in total
919 ms
3.4 sec
421 ms
Welcome to fb.co.nz homepage info - get ready to check Fb best content for Australia right away, or after learning these important things about fb.co.nz
Fletcher Building is a significant employer, manufacturer, home builder, and partner on major construction and infrastructure projects, operating through seven divisions – Building Products, Distribut...
Visit fb.co.nzWe analyzed Fb.co.nz page load time and found that the first response time was 919 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fb.co.nz performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value9.0 s
1/100
25%
Value9.9 s
10/100
10%
Value500 ms
58/100
30%
Value0.137
80/100
15%
Value16.0 s
6/100
10%
919 ms
137 ms
267 ms
883 ms
568 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 56% of them (29 requests) were addressed to the original Fb.co.nz, 8% (4 requests) were made to Ijax.iguana2.com and 8% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fb.co.nz.
Page size can be reduced by 726.3 kB (74%)
985.9 kB
259.7 kB
In fact, the total size of Fb.co.nz main page is 985.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. 55% of websites need less resources to load. Javascripts take 587.9 kB which makes up the majority of the site volume.
Potential reduce by 27.6 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 27.6 kB or 75% of the original size.
Potential reduce by 392.1 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 392.1 kB or 67% of the original size.
Potential reduce by 306.6 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. Fb.co.nz needs all CSS files to be minified and compressed as it can save up to 306.6 kB or 85% of the original size.
Number of requests can be reduced by 22 (49%)
45
23
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fb.co.nz
919 ms
DependencyHandler.axd
137 ms
magnific-popup.css
267 ms
style.css
883 ms
modernizr-2.6.2.min.js
568 ms
ijax_v1.js
385 ms
jquery-1.9.1.min.js
680 ms
DependencyHandler.axd
328 ms
general.js
382 ms
jquery.details.js
473 ms
plugins.js
561 ms
stocks.js
545 ms
analytics.js
49 ms
gp2RmTKtEuI
91 ms
120632078
111 ms
brand-logosv3.png
497 ms
sprite.png
242 ms
fcc_developments.jpg
346 ms
gerard.jpg
368 ms
fb-annual-results-2015-lead-01.jpg
396 ms
Half-year-review-front-page.JPG
452 ms
Ribbon-Cutting-Awtea-Green-170316.jpg
1623 ms
adrian-blake-website-vid.jpg
449 ms
mark-wins-ceo-of-the-year-01.jpg
633 ms
downtown-precinct-2.jpg
514 ms
90-yr-badge.jpg
563 ms
melteca-clipwall-installation-small.jpg
675 ms
doubleGreyBorder.png
547 ms
doubleGreenBorder.png
575 ms
Graphik%20Web-Light.woff
782 ms
Graphik%20Web-Bold.woff
676 ms
Graphik-Regular-Web.woff
766 ms
quote
1237 ms
quote
1241 ms
quote
1246 ms
quote
1249 ms
collect
30 ms
www-embed-player-vflfNyN_r.css
48 ms
www-embed-player.js
89 ms
player.js
197 ms
player.css
187 ms
ga.js
119 ms
vuid.min.js
186 ms
collect
159 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
60 ms
ad_status.js
61 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
59 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
61 ms
__utm.gif
28 ms
proxy.html
22 ms
529705251.jpg
75 ms
arrowUp.png
123 ms
fb.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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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
Image elements do not have [alt] attributes
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>).
fb.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
Browser errors were logged to the console
fb.co.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Fb.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 Fb.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.
fb.co.nz
Open Graph description is not detected on the main page of Fb. 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: