3.9 sec in total
271 ms
3.1 sec
555 ms
Welcome to naomesmo.com.br homepage info - get ready to check Nao Mesmo best content for Brazil right away, or after learning these important things about naomesmo.com.br
Visit naomesmo.com.brWe analyzed Naomesmo.com.br page load time and found that the first response time was 271 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.
naomesmo.com.br performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value10.0 s
0/100
25%
Value17.6 s
0/100
10%
Value4,940 ms
0/100
30%
Value0.002
100/100
15%
Value28.7 s
0/100
10%
271 ms
26 ms
81 ms
87 ms
92 ms
Our browser made a total of 223 requests to load all elements on the main page. We found that 23% of them (52 requests) were addressed to the original Naomesmo.com.br, 17% (38 requests) were made to Cdn.x2n.com.br and 5% (12 requests) were made to Tags.bluekai.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.x2n.com.br.
Page size can be reduced by 454.9 kB (31%)
1.5 MB
1.0 MB
In fact, the total size of Naomesmo.com.br main page is 1.5 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 719.6 kB which makes up the majority of the site volume.
Potential reduce by 115.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 115.9 kB or 77% of the original size.
Potential reduce by 46.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. Nao Mesmo images are well optimized though.
Potential reduce by 223.3 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 223.3 kB or 42% of the original size.
Potential reduce by 69.2 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. Naomesmo.com.br needs all CSS files to be minified and compressed as it can save up to 69.2 kB or 84% of the original size.
Number of requests can be reduced by 80 (49%)
164
84
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nao Mesmo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.naomesmo.com.br
271 ms
css
26 ms
widget.css
81 ms
frontend.css
87 ms
styles.css
92 ms
style.css
92 ms
wpp.css
108 ms
style.css
107 ms
jquery.js
164 ms
jquery-migrate.min.js
128 ms
svg4everybody.min.js
133 ms
blank.js
134 ms
wp-emoji-release.min.js
121 ms
embed.js
21 ms
adsbygoogle.js
5 ms
jquery.form.min.js
121 ms
scripts.js
421 ms
wp-embed.min.js
420 ms
sdk.js
286 ms
_.gif
262 ms
bb_viewability.min.js
36 ms
list
260 ms
bg-socials.png
72 ms
ah-neg%C3%A3o.jpg
72 ms
n%C3%A3o-intedo.jpg
107 ms
insoonia.jpg
73 ms
trollando.jpg
74 ms
nao-leve.jpg
105 ms
omacho.jpg
165 ms
memetizando.jpg
166 ms
humordidoblog.jpg
166 ms
gif.jpg
166 ms
nao-salvo.jpg
192 ms
calango.jpg
192 ms
geraligado.jpg
192 ms
naoligo.jpg
191 ms
mundomemes.jpg
191 ms
AS.jpg
238 ms
dr-pepper.jpg
237 ms
barata.jpg
256 ms
bandeiradois.jpg
239 ms
quadrinhos.jpg
238 ms
humor.jpg
256 ms
incorretos.jpg
286 ms
humorzica.jpg
284 ms
ah-trollei.jpg
286 ms
ah-e-dai.jpg
287 ms
soletrando.jpg
377 ms
mini-lua.jpg
376 ms
bodi.jpg
377 ms
frasestop.jpg
376 ms
chega.jpg
419 ms
F-JaJbplW75-CW3MZ1qMbvesZW2xOQ-xsNqO47m55DA.ttf
58 ms
RkvyadJpQFfhiOnziUIWgPesZW2xOQ-xsNqO47m55DA.ttf
93 ms
hFqlepBer-IXtJK7U5poifesZW2xOQ-xsNqO47m55DA.ttf
92 ms
N9KSa305HxlY5zk6XisHxw.ttf
92 ms
ngiFXK5ukde3w4E-Lmb_OvesZW2xOQ-xsNqO47m55DA.ttf
91 ms
ta-tranquilo.jpg
409 ms
lindos.gif
391 ms
s%C3%B3-eu.jpg
392 ms
ca-pub-9595589933019961.js
120 ms
zrt_lookup.html
145 ms
show_ads_impl.js
85 ms
bg-socials.png
167 ms
ah-neg%C3%A3o.jpg
182 ms
insoonia.jpg
165 ms
trollando.jpg
164 ms
191 ms
naomesmo-1.jpg
318 ms
nao-leve.jpg
151 ms
n%C3%A3o-intedo.jpg
134 ms
xd_arbiter.php
241 ms
xd_arbiter.php
363 ms
omacho.jpg
153 ms
humordidoblog.jpg
152 ms
memetizando.jpg
151 ms
gif.jpg
153 ms
ads
225 ms
osd.js
34 ms
insanos.jpg
143 ms
ads
231 ms
naoligo.jpg
147 ms
calango.jpg
191 ms
nao-salvo.jpg
190 ms
mundomemes.jpg
189 ms
geraligado.jpg
188 ms
ads
274 ms
dr-pepper.jpg
152 ms
AS.jpg
154 ms
quadrinhos.jpg
181 ms
bandeiradois.jpg
180 ms
humor.jpg
165 ms
barata.jpg
160 ms
beacon.js
16 ms
tm11750.js
148 ms
user_sync.html
134 ms
widget.css
22 ms
embed_enabler.min.js
40 ms
humorzica.jpg
137 ms
incorretos.jpg
206 ms
ah-trollei.jpg
205 ms
ah-e-dai.jpg
204 ms
ads
242 ms
pitaco.jpg
158 ms
blogando.jpg
158 ms
bbbeacon-icon-transparent.png
43 ms
250x250.html
278 ms
ads
198 ms
frasestop.jpg
123 ms
mini-lua.jpg
231 ms
bodi.jpg
186 ms
soletrando.jpg
182 ms
m_js_controller.js
157 ms
abg.js
178 ms
showad.js
82 ms
lindos.gif
1288 ms
googlelogo_color_112x36dp.png
260 ms
5171746271700867932
206 ms
naomesmo-1.jpg
235 ms
chega.jpg
303 ms
s%C3%B3-eu.jpg
293 ms
ta-tranquilo.jpg
292 ms
ads
235 ms
universalpixel.js
98 ms
usr
116 ms
PugMaster
151 ms
favicon
166 ms
nessie_icon_tiamat_white.png
74 ms
13159969690191655736
121 ms
s
103 ms
x_button_blue2.png
71 ms
req
247 ms
runtime.js
166 ms
embed_triggers.min.js
54 ms
pixel
72 ms
Pug
71 ms
usersync.aspx
67 ms
B88669EA-05D8-4FB8-B279-67B0BB8AC48B
64 ms
js
299 ms
Pug
38 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
23 ms
Pug
156 ms
Pug
156 ms
Pug
147 ms
Pug
71 ms
03464885388221629
465 ms
Pug
55 ms
img
88 ms
pixel
89 ms
ck-confirm
118 ms
ads
403 ms
list
330 ms
Q116_Wu_Com_AwarenessM_V4_D_300x250_EN_US.jpg
329 ms
lidar.js
18 ms
sbhK2lTE.js
18 ms
naomesmo-logo.png
325 ms
small.js
17 ms
cTrvNaRi.html
233 ms
analytics.js
296 ms
40 ms
graph.facebook.com
186 ms
naomesmo-logo.png
96 ms
4237973346329107795
57 ms
728x90.html
222 ms
collect
47 ms
dpx.js
43 ms
like.php
89 ms
tpid=1DE70445AB0AD5562A032737020267DF
21 ms
like.php
156 ms
p
79 ms
like.php
148 ms
like.php
148 ms
like.php
147 ms
activeview
68 ms
L70CG02Crze.js
298 ms
UPug
57 ms
LVx-xkvaJ0b.png
327 ms
dpx
3 ms
match_redirect
6 ms
pixel.js
45 ms
29931
33 ms
match_redirect
5 ms
0638004977535273
387 ms
tpid=CD29559EAB0AD556CA19503702CE2181
6 ms
dpsync.html
48 ms
lr
3 ms
55 ms
req
71 ms
tc.js
9 ms
lr.gif
9 ms
p
55 ms
match_redirect
3 ms
sync
10 ms
match_redirect
3 ms
CD29559EAB0AD556CA19503702CE2181
40 ms
req
47 ms
match_redirect
23 ms
ProfilesEngineServlet
95 ms
v2
67 ms
ProfilesEngineServlet
44 ms
dpx
6 ms
27519
39 ms
xrefid.xgi
16 ms
pixel
31 ms
generic
13 ms
i.match
156 ms
tap.php
14 ms
1407
160 ms
generic
9 ms
2964
14 ms
3085
45 ms
5386
28 ms
2831
84 ms
2981
64 ms
4448
17 ms
13583
33 ms
4470
78 ms
exelate
3 ms
match_redirect
4 ms
52154.gif
7 ms
i.match
94 ms
engine
96 ms
4229
19 ms
naomesmo.com.br 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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
naomesmo.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
naomesmo.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Naomesmo.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 Naomesmo.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.
naomesmo.com.br
Open Graph description is not detected on the main page of Nao Mesmo. 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: