16.2 sec in total
2.4 sec
4.5 sec
9.3 sec
Welcome to franciscocapelo.net homepage info - get ready to check Franciscocapelo best content right away, or after learning these important things about franciscocapelo.net
Galeria Online - Artistas Visuais de Talento | Desesperadamente à procura de QUALIDADE
Visit franciscocapelo.netWe analyzed Franciscocapelo.net page load time and found that the first response time was 2.4 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
franciscocapelo.net performance score
2394 ms
48 ms
59 ms
324 ms
348 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Franciscocapelo.net, 28% (20 requests) were made to Static.parastorage.com and 13% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Itutor.pt.
Page size can be reduced by 774.3 kB (74%)
1.0 MB
265.6 kB
In fact, the total size of Franciscocapelo.net main page is 1.0 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. 60% of websites need less resources to load. HTML takes 894.2 kB which makes up the majority of the site volume.
Potential reduce by 753.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 753.1 kB or 84% of the original size.
Potential reduce by 434 B
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. Franciscocapelo images are well optimized though.
Potential reduce by 20.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 20.8 kB or 27% of the original size.
Number of requests can be reduced by 8 (15%)
55
47
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Franciscocapelo. 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 as a result speed up the page load time.
www.itutor.pt
2394 ms
bt
48 ms
minified.js
59 ms
fetch.umd.js
324 ms
bolt-custom-elements.min.js
348 ms
requirejs.min.js
348 ms
bolt-performance
11 ms
dynamicmodel
70 ms
wixcode-worker.js
335 ms
wix-perf-measure.bundle.min.js
143 ms
siteTags.bundle.min.js
143 ms
logo_lisbon_tutor_pt2.png
668 ms
chatbutton_24px.png
627 ms
staticCss.min.css
90 ms
UpgradeBrowser.js
46 ms
9546d555308374fa382e853bb02fddc5.jpg
223 ms
england_english_flag.png
647 ms
29d20c_e0a8b154cb054668aca759f7b6e7d6de~mv2.jpg
737 ms
29d20c_94794d79c0f34dc6a2b8626e6a3fe5b2~mv2.jpg
659 ms
29d20c_86514bd450124fecb8f686b385e38628~mv2_d_4592_3448_s_4_2.jpg
657 ms
29d20c_3bd420dacc0b4d5fa4f8d6a3099364df~mv2.jpg
542 ms
29d20c_77d8ec4dc7ec49918c5e1487928a45f7~mv2.jpg
905 ms
foto_eu_estudio_novo.png
900 ms
20180506_161515.png
988 ms
pintura17_glen.jpg
866 ms
foto_eu_5dois.png
923 ms
83c5b99cb1344ae1b625d133cdb2905c.jpg
738 ms
Avatar%20100.png
1001 ms
Avatar%2089.png
1059 ms
Avatar%20108.png
1012 ms
desenho_5_1000.png
1108 ms
pintura_azul.jpg
1263 ms
book_3_language_pipes.jpg
1266 ms
amazon%20logo.png
1274 ms
udemy_logo.png
1298 ms
29d20c_01abaa7068b8496b814f3eabae99227a~mv2.jpg
1418 ms
Graduation%20Caps.jpg
1211 ms
Green%20Typewriter.jpg
1348 ms
In%20the%20Classroom.jpg
1566 ms
d83bd3c21df94d5286771b9bc07e8541.jpg
1394 ms
dce61e681e78441bae6c80aa101ba435.png
1496 ms
favicon_artist2tres2dois_2.png
1744 ms
8d13be_8f66f14740c040529b1929aa09dd8637.png
1350 ms
8d13be_3222e72715fa4a158fc534ae9a1f8d3e.png
1439 ms
8d13be_86d271a32fa44d9798227f619f1ac859~mv2.png
1413 ms
8d13be_f48733a264314321b70f768e29af2150~mv2.png
1415 ms
8d13be_ee68e3211ddc461a87928b5b300582db.png
1521 ms
8d13be_27040962cc0049e3b9c0b761df2eed4b.png
1578 ms
29d20c_9ce51e8f23954c349c8887a2d3b165f0~mv2.png
1750 ms
fadenotchlinenew.png
93 ms
liftedshadow_medium.png
213 ms
bt
150 ms
scotcht.png
126 ms
scotchb.png
157 ms
shadowtop.png
143 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtY.ttf
194 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtY.ttf
255 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
349 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
352 ms
opensans-regular-webfont.woff
85 ms
opensans-bold-webfont.woff
110 ms
neILzCirqoswsqX9zoKmNg.ttf
354 ms
80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff
111 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
109 ms
cca525a8-ad89-43ae-aced-bcb49fb271dc.woff
110 ms
DK0eTGXiZjN6yA8zAEyM2UtCETOCmz2wCdel46UOhAM.woff
353 ms
KGBfwabt0ZRLA5W1ywjowW_WCyVccUAWDspcx_4UXqg.woff
353 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7BMSo3Sup5.ttf
349 ms
If2cXTr6YS-zF4S-kcSWSVi_sxjsohD9F50Ruu7B1i03Sup5.ttf
374 ms
e2b9cbeb-fa8e-41cd-8a6a-46044b29ba52.woff
111 ms
lodash.min.js
72 ms
franciscocapelo.net SEO score
![]()
PT
![]()
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Franciscocapelo.net 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 Franciscocapelo.net 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.
franciscocapelo.net
Open Graph data is detected on the main page of Franciscocapelo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: