7.6 sec in total
893 ms
6.3 sec
409 ms
Visit apl.pt now to see the best up-to-date APL content and also check out these interesting facts you probably never knew about apl.pt
A empresa A P L, em Felgueiras (Porto), dedica-se ao comércio de peles, couros e componentes para calçado. Contacte-nos!
Visit apl.ptWe analyzed Apl.pt page load time and found that the first response time was 893 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
apl.pt performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value14.7 s
0/100
25%
Value15.3 s
1/100
10%
Value90 ms
98/100
30%
Value0.085
93/100
15%
Value13.4 s
11/100
10%
893 ms
337 ms
246 ms
235 ms
339 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 18% of them (29 requests) were addressed to the original Apl.pt, 12% (19 requests) were made to Map8.mapas.sapo.pt and 11% (18 requests) were made to Map7.mapas.sapo.pt. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Img.pai.pt.
Page size can be reduced by 1.0 MB (35%)
2.9 MB
1.9 MB
In fact, the total size of Apl.pt main page is 2.9 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 57.1 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 57.1 kB or 79% of the original size.
Potential reduce by 154.2 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. APL images are well optimized though.
Potential reduce by 703.8 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 703.8 kB or 79% of the original size.
Potential reduce by 99.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. Apl.pt needs all CSS files to be minified and compressed as it can save up to 99.8 kB or 88% of the original size.
Number of requests can be reduced by 49 (31%)
158
109
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of APL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pt
893 ms
yui-common-styles.css
337 ms
app-common-styles.css
246 ms
lp-base-styles.css
235 ms
theme-default_alternative.css
339 ms
yui-common-scripts.js
548 ms
app-common-scripts.js
788 ms
lp-base-scripts.js
582 ms
tracking.js
656 ms
SAPOMapsAPI.js
862 ms
edit-opening-hours-styles.css
580 ms
edit-opening-hours-scripts.js
642 ms
sso.js
324 ms
modernizr.js
766 ms
bingmap7.css
473 ms
yellowMapIframe.js
285 ms
css
37 ms
print-styles.css
124 ms
Style.css
111 ms
fe8a102a-b53b-4afb-8064-6aadb2aa8161_LARGE.png
4224 ms
5px
299 ms
ico_share.png
431 ms
icons-links.gif
278 ms
ico_open.gif
236 ms
landingpage-sprites.png
861 ms
facebook_button.png
295 ms
searchbarbg.jpg
431 ms
footerSearchBarBtnBg.jpg
332 ms
wtid.js
48 ms
directions7.js
361 ms
009.png
644 ms
010.png
653 ms
010.png
745 ms
009.png
342 ms
008.png
340 ms
010.png
649 ms
008.png
530 ms
mapas_escala.gif
320 ms
309.jpeg
528 ms
loadBooking.ajah;jsessionid=33A072A3567549A58A8C3A03927BA6A8
249 ms
checkMobile.ajaj;jsessionid=33A072A3567549A58A8C3A03927BA6A8
298 ms
loadBookingForWT.ajah;jsessionid=33A072A3567549A58A8C3A03927BA6A8
354 ms
347 ms
309.png
260 ms
115.jpeg
595 ms
114.jpeg
601 ms
116.jpeg
596 ms
115.png
388 ms
114.png
613 ms
116.png
611 ms
nyMarker.png
431 ms
008.jpeg
323 ms
008.png
424 ms
309.jpeg
426 ms
310.jpeg
430 ms
309.png
338 ms
310.png
535 ms
115.jpeg
870 ms
116.jpeg
934 ms
114.jpeg
951 ms
115.png
636 ms
116.png
649 ms
114.png
771 ms
3048cba1287c3ec9f63a5f4faaf3aea375cf2ad5add677a2bc4d24b43aec6337.png
212 ms
mapas_escalaw.gif
210 ms
619f74c2eda1e2d9d500e02151fcd9583f16f7ba837aa064325a20ceee587490.png
214 ms
arrow_up.gif
212 ms
arrow_left.gif
216 ms
arrow_center.gif
300 ms
arrow_right.gif
313 ms
arrow_down.gif
313 ms
plus.gif
314 ms
minus.gif
317 ms
zoom_point.gif
318 ms
zoom_select.gif
404 ms
status_btn.png
417 ms
zoom_circle.png
417 ms
zoom_in.png
417 ms
zoom_slide.png
423 ms
zoom_out.png
422 ms
010.jpeg
430 ms
010.png
428 ms
114.jpeg
547 ms
115.jpeg
536 ms
114.png
324 ms
115.png
570 ms
009.png
541 ms
008.png
535 ms
010.jpeg
540 ms
009.jpeg
648 ms
008.jpeg
435 ms
010.png
875 ms
009.png
938 ms
008.png
1005 ms
311.jpeg
958 ms
310.jpeg
990 ms
311.png
977 ms
310.png
1093 ms
009.png
538 ms
010.jpeg
638 ms
009.jpeg
429 ms
010.png
530 ms
009.png
433 ms
311.jpeg
853 ms
311.png
660 ms
114.jpeg
958 ms
114.png
856 ms
009.png
217 ms
008.jpeg
319 ms
009.jpeg
324 ms
008.png
214 ms
009.png
223 ms
310.jpeg
631 ms
309.jpeg
635 ms
311.jpeg
638 ms
310.png
433 ms
309.png
537 ms
311.png
537 ms
116.jpeg
967 ms
115.jpeg
1068 ms
114.jpeg
994 ms
116.png
950 ms
115.png
856 ms
114.png
856 ms
010.png
220 ms
008.png
537 ms
009.jpeg
420 ms
010.jpeg
319 ms
008.jpeg
422 ms
009.png
641 ms
010.png
532 ms
008.png
844 ms
311.jpeg
849 ms
310.jpeg
922 ms
309.jpeg
956 ms
311.png
853 ms
310.png
862 ms
309.png
1063 ms
116.jpeg
1386 ms
116.png
1078 ms
008.png
531 ms
010.png
533 ms
009.jpeg
316 ms
008.jpeg
540 ms
010.jpeg
320 ms
009.png
406 ms
008.png
742 ms
010.png
743 ms
310.jpeg
830 ms
311.jpeg
987 ms
309.jpeg
991 ms
310.png
881 ms
311.png
1057 ms
309.png
957 ms
116.jpeg
1360 ms
115.jpeg
1485 ms
116.png
1175 ms
115.png
1221 ms
KzHY9N-PIagGI86CpWfnZA.ttf
11 ms
dcs.gif
44 ms
wa.gif
430 ms
plusone.js
67 ms
apl.pt 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.
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
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.
apl.pt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
apl.pt SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apl.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Apl.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.
apl.pt
Open Graph data is detected on the main page of APL. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: