5 sec in total
809 ms
3.6 sec
585 ms
Click here to check amazing My Place Office content for Brazil. Otherwise, check out these important facts you probably never knew about myplaceoffice.com.br
É empreendedor e precisa de um escritório com boa infraestrutura para trabalhar? Confira os escritórios compartilhados da My Place!
Visit myplaceoffice.com.brWe analyzed Myplaceoffice.com.br page load time and found that the first response time was 809 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
myplaceoffice.com.br performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value19.1 s
0/100
25%
Value18.3 s
0/100
10%
Value2,120 ms
7/100
30%
Value0.098
90/100
15%
Value18.6 s
3/100
10%
809 ms
218 ms
233 ms
107 ms
107 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 61% of them (65 requests) were addressed to the original Myplaceoffice.com.br, 7% (7 requests) were made to Apis.google.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Myplaceoffice.com.br.
Page size can be reduced by 1.5 MB (38%)
4.1 MB
2.5 MB
In fact, the total size of Myplaceoffice.com.br main page is 4.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. 75% 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. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 56.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. This page needs HTML code to be minified as it can gain 17.8 kB, which is 26% 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 56.1 kB or 83% of the original size.
Potential reduce by 503.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. Obviously, My Place Office needs image optimization as it can save up to 503.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 675.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 675.5 kB or 71% of the original size.
Potential reduce by 299.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. Myplaceoffice.com.br needs all CSS files to be minified and compressed as it can save up to 299.8 kB or 84% of the original size.
Number of requests can be reduced by 48 (50%)
96
48
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Place Office. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.myplaceoffice.com.br
809 ms
jquery-1.11.0.min.js
218 ms
style.css
233 ms
modernizr.custom.63321.js
107 ms
slick.css
107 ms
jquery.fancybox.css
118 ms
jquery.fancybox.pack.js
212 ms
jquery.min.js
32 ms
jquery-scrolltofixed.js
204 ms
jquery-ui-1.10.4.custom.js
356 ms
jquery.bxslider.js
269 ms
jquery.stickem.js
201 ms
jquery.scrollTo.min.js
215 ms
jquery.dropdown.js
245 ms
responsiveTabs.js
288 ms
scripts.js
288 ms
placeholders.js
20 ms
slick.js
457 ms
conversion.js
26 ms
html5reset-1.6.1.css
202 ms
jquery-ui-1.10.4.custom.css
242 ms
jquery.bxslider.css
245 ms
custom_select.css
262 ms
css
25 ms
wp-emoji-release.min.js
148 ms
ga.js
44 ms
logo.png
137 ms
unidade-a.jpg
138 ms
unidade-centro.jpg
136 ms
Unidade-Faria-Lima.jpg
136 ms
paulista-thumb.jpg
137 ms
unidade-paulista-01-210x210.jpg
389 ms
Unidade-Ipiranga.jpg
388 ms
rio-icone.jpg
387 ms
unidade-florianopolis.jpg
389 ms
unidade-florianopolis-dois.jpg
389 ms
slider-escritorio-virtual.jpg
707 ms
01.jpg
1165 ms
03.jpg
993 ms
02.jpg
1024 ms
IMG_1890-210x210.jpg
497 ms
sp-paulista-thumb-210x210.jpg
502 ms
10476527_1520177114923861_1215224067039672705_o-210x210.jpg
703 ms
01-1-210x210.jpg
685 ms
EB131010_0761-210x210.jpg
1021 ms
EB131010_1461-210x210.jpg
1021 ms
EB131104_bc1821-210x210.jpg
1109 ms
EB131104_bc0502-210x210.jpg
1186 ms
sdk.js
376 ms
Q0G_4uXmXIE
365 ms
bg_header.png
1147 ms
seta-menu.png
1145 ms
bt-borda.png
1174 ms
bg-separa-menu.png
1121 ms
icone-teste.png
1328 ms
bg-separa-menu-unidades.png
1238 ms
bt-bg-topo.png
1317 ms
type_list_check.png
1246 ms
btn_saibamais.png
1245 ms
__utm.gif
68 ms
bt-enviar.png
1262 ms
widgets.js
258 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
58 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
57 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
57 ms
platform.js
328 ms
ico_rbianco.png
1314 ms
collect
281 ms
279 ms
fbds.js
273 ms
sem-custos-adicionais.html
1126 ms
www-embed-player-vflQrT_sR.css
194 ms
www-embed-player.js
327 ms
base.js
454 ms
fancybox_overlay.png
1007 ms
fancybox_sprite.png
1066 ms
fancybox_loading.gif
1089 ms
bt-bg-botao.png
1169 ms
bts-bg-servicos.jpg
1475 ms
ajax-loader.gif
1118 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
325 ms
ga-audiences
242 ms
slick.woff
1087 ms
318 ms
cb=gapi.loaded_0
46 ms
cb=gapi.loaded_1
121 ms
fastbutton
197 ms
xd_arbiter.php
284 ms
xd_arbiter.php
528 ms
327 ms
269 ms
postmessageRelay
208 ms
cb=gapi.loaded_0
111 ms
cb=gapi.loaded_1
111 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
295 ms
tweet_button.6a78875565a912489e9aef879c881358.pt.html
171 ms
api.js
189 ms
core:rpc:shindig.random:shindig.sha1.js
263 ms
2536007149-postmessagerelay.js
201 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
64 ms
ad_status.js
144 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
36 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
jot
103 ms
jquery.min.js
267 ms
jquery.js
373 ms
jquery-migrate.min.js
189 ms
myplaceoffice.com.br 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
myplaceoffice.com.br 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
myplaceoffice.com.br 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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myplaceoffice.com.br 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 Myplaceoffice.com.br 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.
myplaceoffice.com.br
Open Graph data is detected on the main page of My Place Office. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: