1.5 sec in total
79 ms
937 ms
523 ms
Click here to check amazing Postcode content for United States. Otherwise, check out these important facts you probably never knew about postcode.io
The domain name postcode.io is for sale. Make an offer or buy it now at a set price.
Visit postcode.ioWe analyzed Postcode.io page load time and found that the first response time was 79 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
postcode.io performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.6 s
61/100
25%
Value3.8 s
83/100
10%
Value140 ms
96/100
30%
Value0.029
100/100
15%
Value6.3 s
60/100
10%
79 ms
135 ms
14 ms
25 ms
28 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 41% of them (18 requests) were addressed to the original Postcode.io, 16% (7 requests) were made to Fonts.gstatic.com and 9% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (334 ms) relates to the external source Fonts.googleapis.com.
Page size can be reduced by 85.1 kB (13%)
649.8 kB
564.7 kB
In fact, the total size of Postcode.io main page is 649.8 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. 50% of websites need less resources to load. Images take 485.7 kB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 17% 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 12.5 kB or 73% of the original size.
Potential reduce by 48.7 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. Postcode images are well optimized though.
Potential reduce by 20.7 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 20.7 kB or 15% of the original size.
Potential reduce by 3.2 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. Postcode.io needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 75% of the original size.
Number of requests can be reduced by 15 (45%)
33
18
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Postcode. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
postcode.io
79 ms
www.postcode.io
135 ms
bootstrap.min.css
14 ms
custom.css
25 ms
responsive.css
28 ms
jquery.min.js
32 ms
custom.js
29 ms
popover-v1.js
36 ms
jquery.js
7 ms
bootstrap.min.js
46 ms
conversion.js
25 ms
css
24 ms
css
35 ms
css
46 ms
css
334 ms
nextrequest_logo_color-6a7f6959201821ba93e88e7f66da9185.png
197 ms
SanFrancisco.jpg
58 ms
9226d4faf3f1a9c32e1b6fab6388dc7c30594093.jpg
275 ms
postcode_logo_400px.png
53 ms
down_arrow.png
55 ms
products_image.jpg
61 ms
recordtrac_logo_notext.png
55 ms
promptly_logo_notext.png
64 ms
cityvoice_logo_notext.png
66 ms
twitter_logo.png
66 ms
facebook_logo.png
65 ms
linkedin_logo.png
64 ms
zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff
10 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
118 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
120 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
119 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
118 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
118 ms
widgets.js
148 ms
ga.js
57 ms
102 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
52 ms
glyphicons-halflings-regular.woff
53 ms
fbds.js
47 ms
jquery.fancybox.css
95 ms
__utm.gif
17 ms
94 ms
51 ms
22 ms
postcode.io 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-*] attributes do not have valid values
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
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
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
postcode.io 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
Page has valid source maps
postcode.io 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postcode.io 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 Postcode.io 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.
postcode.io
Open Graph description is not detected on the main page of Postcode. 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: