5.2 sec in total
268 ms
3.1 sec
1.8 sec
Click here to check amazing Cpmoffice content for Brazil. Otherwise, check out these important facts you probably never knew about cpmoffice.com.br
Na Marpax você encontra tudo o que precisa pelo melhor custo-benefício, temos produtos de Escritório, Papelaria e Artesanato. Confira na Loja Oficial as Ofertas!
Visit cpmoffice.com.brWe analyzed Cpmoffice.com.br page load time and found that the first response time was 268 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cpmoffice.com.br performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value9.2 s
1/100
25%
Value17.2 s
0/100
10%
Value5,820 ms
0/100
30%
Value0.214
58/100
15%
Value25.8 s
0/100
10%
268 ms
836 ms
85 ms
42 ms
50 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cpmoffice.com.br, 63% (106 requests) were made to Marpax.fbitsstatic.net and 5% (8 requests) were made to Conectiva.io. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Mc.yandex.ru.
Page size can be reduced by 444.2 kB (21%)
2.1 MB
1.7 MB
In fact, the total size of Cpmoffice.com.br main page is 2.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. 85% 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 257.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 257.6 kB or 87% of the original size.
Potential reduce by 185.1 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, Cpmoffice needs image optimization as it can save up to 185.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 11 B
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. Cpmoffice.com.br has all CSS files already compressed.
Number of requests can be reduced by 51 (31%)
162
111
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cpmoffice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cpmoffice.com.br
268 ms
www.marpax.com.br
836 ms
gtm.js
85 ms
css2
42 ms
50 ms
swiper-bundle.min.css
26 ms
51 ms
swiper-bundle.min.js
40 ms
52 ms
pushnews-launcher.js
152 ms
TrayCorp.min.js
644 ms
yvapi.js
468 ms
b82a4459-a1da-412a-93b2-946ceb5cd318.gif
161 ms
logo.png
4 ms
b0a6888c-2440-4b62-8b0b-62778fb3a4b5.png
74 ms
a34eccfb-d13b-45e7-b14b-95715ba30711.png
111 ms
1c3bbd90-5b30-4e6c-8d70-5a13e41aa785.png
112 ms
1b5ed7f4-20b3-41da-a320-3535a01c9e33.png
113 ms
4e97a6d1-0a5c-4bb5-95c4-5b95961d7851.png
515 ms
6836a7d8-79a4-4ad4-a332-3a4239cdbd82.png
126 ms
a84ace28-766c-4620-9e3c-384cb365ef9b.png
312 ms
9720b37d-26e9-40e2-9154-2e85f081b332.png
161 ms
a9a2f453-f8b9-46ae-9165-c2d23c232282.png
161 ms
bb34d2ac-f571-4192-934e-54e7b9823b00.png
444 ms
208dc125-ea7b-471c-911a-579f10534a61.png
465 ms
257253.jpg
463 ms
257253-1.jpg
464 ms
recurrence-img.png
515 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
463 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
547 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
618 ms
js
263 ms
493 ms
analytics.js
456 ms
core.js
455 ms
bat.js
487 ms
hotjar-3615679.js
544 ms
yvapi.js
642 ms
h4i1o0tz99
552 ms
load.js
600 ms
all.min.js
531 ms
tag.js
1156 ms
maxresdefault.jpg
565 ms
259164-4.jpg
434 ms
259164-2.jpg
441 ms
259231.jpg
442 ms
259231-1.jpg
443 ms
258317.jpg
503 ms
258317-1.jpg
492 ms
55ed40f8-29bc-4213-bab1-ff378cb7d3fe.png
564 ms
8b33d260-b30a-4083-b9d9-0cc7fd525ca5.png
512 ms
6697f580-90ff-4808-ac8b-110275a25197.png
562 ms
4f7fe9d1-b2d3-429d-8330-b3388658d5e9.png
562 ms
d37ea83f-c0f3-447a-b986-6e76d4dce760.png
563 ms
6c84d174-d35a-491e-b013-7132c9d73619.gif
719 ms
258086.jpg
563 ms
258086-1.jpg
567 ms
258087.jpg
566 ms
258087-1.jpg
565 ms
257643.jpg
567 ms
257643-1.jpg
567 ms
256781.jpg
599 ms
256781-1.jpg
599 ms
257846.jpg
599 ms
257846-1.jpg
600 ms
mqdefault.jpg
565 ms
mqdefault.jpg
598 ms
257973.jpg
598 ms
257973-1.jpg
602 ms
bqloader.js
496 ms
integration.min.js
486 ms
storefront-sdk.min.js
553 ms
589 ms
chat-widget.min.js
494 ms
256789.jpg
586 ms
256789-1.jpg
552 ms
257972.jpg
552 ms
259268.jpg
553 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
3 ms
259268-1.jpg
403 ms
256974-16.jpg
272 ms
256974-17.jpg
253 ms
256903.jpg
253 ms
256976.jpg
206 ms
256976-1.jpg
205 ms
collect
86 ms
909ab0d2-6875-4e51-a69f-19233eb8b0c1.gif
593 ms
256962.jpg
180 ms
256962-1.jpg
273 ms
256964.jpg
176 ms
256964-1.jpg
175 ms
125 ms
256966.jpg
125 ms
343051232.js
69 ms
256966-1.jpg
213 ms
modules.2472296d2d26f0040059.js
98 ms
collect
101 ms
256967.jpg
201 ms
clarity.js
89 ms
256967-1.jpg
152 ms
256965.jpg
155 ms
256965-1.jpg
154 ms
256963.jpg
154 ms
256963-1.jpg
152 ms
257642.jpg
165 ms
257642-1.jpg
164 ms
256968.jpg
162 ms
256968-1.jpg
162 ms
256646-4.jpg
164 ms
343051232
42 ms
160 ms
146 ms
256646-5.jpg
142 ms
256669-16.jpg
141 ms
256669-17.jpg
141 ms
259275.jpg
140 ms
259275-1.jpg
151 ms
257299.jpg
151 ms
257299-1.jpg
151 ms
259223.jpg
150 ms
259223-1.jpg
150 ms
257089-1.jpg
149 ms
259171.jpg
245 ms
257656.jpg
243 ms
257656-1.jpg
243 ms
256922.jpg
241 ms
256922-1.jpg
239 ms
marpax.png
242 ms
elgin.png
241 ms
ga-audiences
106 ms
bright.png
241 ms
filipaper.png
239 ms
brw.png
237 ms
jquery-3.6.0.min.js
122 ms
menno.png
209 ms
6350.js
200 ms
selos.js
356 ms
platform.js
198 ms
fbevents.js
106 ms
events.js
248 ms
aurora.png
143 ms
background-newsletter-marpax-4.png
362 ms
google-safe-2.png
180 ms
loja-protegida.png
180 ms
google-safe-1.png
178 ms
master.jpg
180 ms
elo.jpg
180 ms
visa.jpg
180 ms
barcode.jpg
179 ms
core.js
35 ms
hiper.jpg
172 ms
americanexpress.jpg
170 ms
eficaz-logo.png
170 ms
wake-logo.png
169 ms
load.js
245 ms
chat-widget.min.css
93 ms
icon-collapse.svg
235 ms
GetConfig
134 ms
6350.js
69 ms
datatunnel.js
22 ms
visitor.js
22 ms
cartstackbr.js
23 ms
performa.js
21 ms
229 ms
pgvw.png
71 ms
all.min.js
83 ms
advert.gif
669 ms
c.gif
7 ms
sync_cookie_image_decide
132 ms
cpmoffice.com.br accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible 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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
cpmoffice.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cpmoffice.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Cpmoffice.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 Cpmoffice.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.
cpmoffice.com.br
Open Graph description is not detected on the main page of Cpmoffice. 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: