4.2 sec in total
494 ms
3.5 sec
186 ms
Visit infobel.pt now to see the best up-to-date Infobel content for Portugal and also check out these interesting facts you probably never knew about infobel.pt
Busca em toda a Portugal com o directório telefónico online, busca no directório de Empresas e no directório de particulares!
Visit infobel.ptWe analyzed Infobel.pt page load time and found that the first response time was 494 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
infobel.pt performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.9 s
6/100
25%
Value4.6 s
71/100
10%
Value460 ms
62/100
30%
Value0.75
6/100
15%
Value9.0 s
33/100
10%
494 ms
66 ms
67 ms
98 ms
33 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Infobel.pt, 13% (11 requests) were made to Infobel.com and 8% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (798 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 744.9 kB (65%)
1.1 MB
393.8 kB
In fact, the total size of Infobel.pt main page is 1.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. 80% 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. Javascripts take 531.5 kB which makes up the majority of the site volume.
Potential reduce by 81.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. 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 81.9 kB or 84% of the original size.
Potential reduce by 28.4 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, Infobel needs image optimization as it can save up to 28.4 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 295.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 295.5 kB or 56% of the original size.
Potential reduce by 339.1 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. Infobel.pt needs all CSS files to be minified and compressed as it can save up to 339.1 kB or 84% of the original size.
Number of requests can be reduced by 50 (68%)
74
24
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Infobel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
494 ms
css
66 ms
kendo.common.min.css
67 ms
kendo.default.min.css
98 ms
bootstrap.min.css
33 ms
css
117 ms
css
319 ms
ads.js
99 ms
adsbygoogle.js
47 ms
cookieconsent.min.js
51 ms
jquery-2.1.4.min.js
47 ms
jquery
289 ms
kendo.core.min.js
90 ms
kendo.data.min.js
94 ms
kendo.popup.min.js
92 ms
kendo.list.min.js
93 ms
kendo.autocomplete.min.js
95 ms
kendo.dropdownlist.min.js
94 ms
kendo.panelbar.min.js
95 ms
kendo.tooltip.min.js
98 ms
kendo.upload.min.js
157 ms
kendo.combobox.min.js
97 ms
kendo.multiselect.min.js
94 ms
kendo.validator.min.js
85 ms
kendo.aspnetmvc.min.js
85 ms
other
279 ms
custom
175 ms
platform.js
86 ms
in.js
76 ms
ga.js
113 ms
infobel-logo-white.png
127 ms
sdk.js
475 ms
__utm.gif
20 ms
toadOcfmlt9b38dHJxOBGIPZSf8Ud0kNoe3bGnF7K24.woff
44 ms
ODelI1aHBYDBqgeIAH2zlBBHWFfxJXS04xYOz0jw624.woff
59 ms
toadOcfmlt9b38dHJxOBGAAD_zxmsR6vL1X3tnvCZYo.woff
288 ms
world-map.png
289 ms
Infobel-Iconfont.woff
270 ms
ca-pub-7219613918654603.js
265 ms
zrt_lookup.html
446 ms
show_ads_impl.js
253 ms
widgets.js
410 ms
infobel-others.ttf
216 ms
secureAnonymousFramework
451 ms
cb=gapi.loaded_0
397 ms
cb=gapi.loaded_1
395 ms
sharebutton
492 ms
ads
359 ms
inspectlet.js
128 ms
expansion_embed.js
228 ms
osd.js
226 ms
ads
307 ms
452 ms
xd_arbiter.php
451 ms
xd_arbiter.php
798 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
526 ms
1327419040
352 ms
share
321 ms
sprite_connect_v14.png
523 ms
rs=AGLTcCMjQOKLzmHw4jAL4LZH64_0PwYekw
233 ms
rs=AGLTcCM_4QRxOE6D7i046ieS6uXn08HhGg
233 ms
css
342 ms
m_js_controller.js
331 ms
abg.js
332 ms
postmessageRelay
259 ms
vxNK-E6B13CyehuDCmvQvw.woff
266 ms
grlryt2bdKIyfMSOhzd1eA.woff
268 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
96 ms
nessie_icon_thin_arrow_big_white.png
55 ms
googlelogo_color_112x36dp.png
154 ms
api.js
105 ms
core:rpc:shindig.random:shindig.sha1.js
163 ms
2536007149-postmessagerelay.js
174 ms
x_button_blue2.svg
74 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
81 ms
s
44 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
51 ms
dark-top.css
109 ms
jot
109 ms
share_button.php
86 ms
logo.png
22 ms
source_sans_pro_300-webfont.woff
188 ms
nihcf5d8joz.js
486 ms
LVx-xkvaJ0b.png
553 ms
infobel.pt 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 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.
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
Buttons do not have an accessible name
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
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.
infobel.pt 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
infobel.pt 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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infobel.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Infobel.pt 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.
infobel.pt
Open Graph description is not detected on the main page of Infobel. 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: