21.8 sec in total
4.7 sec
16.9 sec
218 ms
Click here to check amazing Androidportugal content. Otherwise, check out these important facts you probably never knew about androidportugal.com
Visit androidportugal.comWe analyzed Androidportugal.com page load time and found that the first response time was 4.7 sec and then it took 17.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
androidportugal.com performance score
4708 ms
388 ms
833 ms
733 ms
771 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 62% of them (39 requests) were addressed to the original Androidportugal.com, 14% (9 requests) were made to Apis.google.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Androidportugal.com.
Page size can be reduced by 401.6 kB (61%)
661.7 kB
260.2 kB
In fact, the total size of Androidportugal.com main page is 661.7 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. Javascripts take 325.8 kB which makes up the majority of the site volume.
Potential reduce by 26.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 26.6 kB or 79% of the original size.
Potential reduce by 108.6 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. Obviously, Androidportugal needs image optimization as it can save up to 108.6 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 233.5 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 233.5 kB or 72% of the original size.
Potential reduce by 32.9 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. Androidportugal.com needs all CSS files to be minified and compressed as it can save up to 32.9 kB or 82% of the original size.
Number of requests can be reduced by 36 (59%)
61
25
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Androidportugal. 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.
www.androidportugal.com
4708 ms
style.css
388 ms
default.css
833 ms
custom.css
733 ms
shortcodes.css
771 ms
jquery.min.js
696 ms
shortcodes.js
746 ms
jquery-ui-1.8.5.custom.min.js
941 ms
superfish.js
859 ms
slides.min.jquery.js
900 ms
custom.js
909 ms
html5.js
1054 ms
widgets.js
6 ms
all.js
9 ms
plusone.js
102 ms
bg-body.png
223 ms
ico-header-rss.png
228 ms
ico-header-email.png
638 ms
ico-header-facebook.png
629 ms
ico-header-twitter.png
268 ms
bg-header.png
227 ms
androidptlogo.png
482 ms
alert-overlay.png
652 ms
ico-search.png
416 ms
bg-secondary-nav.png
645 ms
ico-home.png
650 ms
Project-Glass-Patent.jpeg
660 ms
fullType7-600x300.jpg
902 ms
Project-Glass-Patent-290x150.jpg
830 ms
ico-comment.png
1017 ms
fullType7-290x150.jpg
833 ms
ico-list.png
1017 ms
ico-footer-twitter.png
867 ms
ico-footer-facebook.png
4119 ms
ico-footer-google.png
4121 ms
ico-footer-rss.png
4117 ms
ico-footer-email.png
4791 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
29 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
53 ms
ico-pagination-prev.png
4716 ms
ico-pagination-next.png
4712 ms
195 ms
fastbutton
84 ms
postmessageRelay
97 ms
xd_arbiter.php
45 ms
xd_arbiter.php
71 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
22 ms
rs=AGLTcCOyEe7xIoYbKqvJH6xA3ail6lX-YA
25 ms
cb=gapi.loaded_0
47 ms
cb=gapi.loaded_1
44 ms
3193398744-postmessagerelay.js
61 ms
rpc:shindig_random.js
59 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
90 ms
like.php
129 ms
cb=gapi.loaded_0
11 ms
like.php
143 ms
qeKvIRsJabD.js
44 ms
LVx-xkvaJ0b.png
39 ms
jot.html
2 ms
Project-Glass-Patent.jpeg
373 ms
loader-white.gif
450 ms
ico-slider-pagination.png
278 ms
androidportugal.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Androidportugal.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Androidportugal.com 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.
androidportugal.com
Open Graph description is not detected on the main page of Androidportugal. 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: