ZEMOLEZA.COM.BR Zé Moleza | TCC, monografias e trabalhos feitos. Pesquise já!

zemoleza.com.br Website Information

Daily Unique Visits: 0

Daily Page Views: 0

Income Per Day: $0

Estimated Value: $9

zemoleza.com.br is registered under .BR top-level domain. Please check other sites in .BR zone.

No name server records were found.

and is probably hosted by CLOUDFLARENET - Cloudflare, Inc., US. See the full list of other websites hosted by CLOUDFLARENET - Cloudflare, Inc., US.

The highest website zemoleza.com.br position in Alexa rank database was 5348 and the lowest rank position was 920442. Current position of zemoleza.com.br in Alexa rank database is below 1 million.

Desktop speed score of zemoleza.com.br (79/100) is better than the results of 67.91% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of zemoleza.com.br (64/100) is better than the results of 11.2% of other sites and means that the page is not mobile-friendly.

Mobile speed score of zemoleza.com.br (48/100) is better than the results of 30.32% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

zemoleza.com.br Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


zemoleza.com.br whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


% Copyright (c) Nic.br
% The use of the data below is only permitted as described in
% full by the Use and Privacy Policy at https://registro.br/upp ,
% being prohibited its distribution, commercialization or
% reproduction, in particular, to use it for advertising or
% any similar purpose.
% 2024-09-16T18:18:33-03:00 - IP: 167.99.102.248

% Permission denied. For more information, contact abuse@registro.br

% Security and mail abuse issues should also be addressed to
% cert.br, http://www.cert.br/ , respectivelly to cert@cert.br
% and mail-abuse@cert.br
%
% whois.registro.br accepts only direct match queries. Types
% of queries are: domain (.br), registrant (tax ID), ticket,
% provider, CIDR block, IP and ASN.

zemoleza.com.br server information

Servers Location

zemoleza.com.br desktop page speed rank

Last tested: 2019-12-15


Desktop Speed Medium
79/100

zemoleza.com.br Desktop Speed Test Quick Summary


priority - 9Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://zemoleza.com.br/
https://zemoleza.com.br/
https://www.zemoleza.com.br/

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 15 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

https://www.zemoleza.com.br/wp-content/cache/busti…ry/jquery-1.12.4-wp.js
https://www.zemoleza.com.br/wp-content/cache/busti…y-migrate.min-1.4.1.js
https://www.zemoleza.com.br/wp-content/plugins/wp-favorite-posts/wpfp.js

Optimize CSS Delivery of the following:

https://www.zemoleza.com.br/wp-content/plugins/wp-favorite-posts/wpfp.css
https://www.zemoleza.com.br/wp-includes/css/dist/b…-library/style.min.css
https://www.zemoleza.com.br/wp-content/cache/busti…blocks/style-3.6.5.css
https://www.zemoleza.com.br/wp-content/cache/busti…s/css/styles-5.1.3.css
https://www.zemoleza.com.br/wp-content/cache/busti…ratings-css-1.86.2.css
https://www.zemoleza.com.br/wp-content/cache/busti…osuggest.min-3.1.1.css
https://www.zemoleza.com.br/wp-content/cache/busti…s/facets.min-3.1.1.css
https://www.zemoleza.com.br/wp-includes/css/dashicons.min.css
https://www.zemoleza.com.br/wp-includes/js/thickbox/thickbox.css
https://www.zemoleza.com.br/wp-content/cache/busti…/css/front-7.12.30.css
https://fonts.googleapis.com/css?family=Open+Sans:400,700,400italic
https://www.zemoleza.com.br/wp-content/themes/zemo…/css/bootstrap.min.css
https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/style.css
https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/css/lightbox.css
https://www.zemoleza.com.br/wp-content/themes/zemo…-v2/css/menu/trunk.css

priority - 6Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://static.hotjar.com/c/hotjar-959296.js?sv=5 (60 seconds)
https://rec.smartlook.com/recorder.js (10 minutes)
https://securepubads.g.doubleclick.net/tag/js/gpt.js (15 minutes)
https://www.google-analytics.com/gtm/js?id=GTM-5KN…d=810651782.1576428342 (15 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-KK7SR4 (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/pt_BR/sdk.js (20 minutes)
https://connect.facebook.net/signals/config/388695…0651?v=2.9.15&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 9.9KiB (17% reduction).

Compressing https://www.zemoleza.com.br/wp-content/themes/zemo…/about-page-cricle.png could save 2.9KiB (11% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/images/logo.png could save 1.7KiB (14% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemo…2/images/foot-logo.png could save 1.2KiB (14% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/images/prev.png could save 1KiB (74% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/images/next.png could save 997B (73% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/images/search.png could save 985B (59% reduction).
Compressing https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/images/mob-i1.jpg could save 766B (28% reduction).
Compressing https://www.zemoleza.com.br/wp-content/plugins/wp-…rystal/rating_over.gif could save 365B (37% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.9KiB (28% reduction).

Minifying https://www.zemoleza.com.br/wp-content/cache/busti…ickbox-3.1-20121105.js could save 1.2KiB (32% reduction) after compression.
Minifying https://connect.facebook.net/pt_BR/sdk.js could save 673B (39% reduction) after compression.
Minifying https://www.zemoleza.com.br/wp-content/cache/busti…es/js/scripts-5.1.3.js could save 653B (17% reduction) after compression.
Minifying https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/js/zemoleza.js could save 424B (30% reduction) after compression.

priority - 0Reduce server response time

In our test, your server responded in 0.23 seconds.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2KiB (14% reduction).

Minifying https://www.zemoleza.com.br/wp-content/themes/zemoleza-v2/style.css could save 1.4KiB (12% reduction) after compression.
Minifying https://www.zemoleza.com.br/wp-content/themes/zemo…-v2/css/menu/trunk.css could save 317B (19% reduction) after compression.
Minifying https://www.zemoleza.com.br/wp-content/cache/busti…ratings-css-1.86.2.css could save 228B (55% reduction) after compression.

zemoleza.com.br Desktop Resource Breakdown

Total Resources93
Number of Hosts29
Static Resources63
JavaScript Resources36
CSS Resources15

zemoleza.com.br mobile page speed rank

Last tested: 2016-10-13


Mobile Speed Bad
48/100

zemoleza.com.br Mobile Speed Test Quick Summary


priority - 48Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 12 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://zemolezaus.s3.amazonaws.com/wp-includes/js/…y/jquery.js?ver=1.11.0
http://zemolezaus.s3.amazonaws.com/wp-includes/js/…grate.min.js?ver=1.2.1
http://zemolezaus.s3.amazonaws.com/wp-content/plug…ftype.min.js?ver=3.9.1
http://zemolezaus.s3.amazonaws.com/wp-content/plug…osts/wpfp.js?ver=3.9.1
http://s7.addthis.com/js/300/addthis_widget.js
http://zemolezaus.s3.amazonaws.com/wp-content/them…query.jcarousel.min.js
http://zemolezaus.s3.amazonaws.com/wp-content/them…ery.maskedinput.min.js

Optimize CSS Delivery of the following:

http://zemolezaus.s3.amazonaws.com/wp-content/themes/zemoleza/style.css
http://zemolezaus.s3.amazonaws.com/wp-content/plug…avorite-posts/wpfp.css
http://zemolezaus.s3.amazonaws.com/wp-content/plug…my-login.css?ver=6.3.8
http://zemolezaus.s3.amazonaws.com/wp-content/plug…s/output.css?ver=3.9.1
http://zemolezaus.s3.amazonaws.com/wp-content/plug…s/styles.css?ver=3.8.1
http://zemolezaus.s3.amazonaws.com/wp-content/plug…complete.css?ver=3.9.1
http://zemolezaus.s3.amazonaws.com/wp-content/plug…-layout.css?ver=2.1.12
http://zemolezaus.s3.amazonaws.com/wp-content/plug…ommerce.css?ver=2.1.12
http://zemolezaus.s3.amazonaws.com/wp-content/plug…rk/style.css?ver=2.8.3
http://zemolezaus.s3.amazonaws.com/wp-content/plug…lt/style.css?ver=2.8.3
http://zemolezaus.s3.amazonaws.com/wp-content/plug…rd/style.css?ver=2.8.3
http://zemolezaus.s3.amazonaws.com/wp-content/plug…ls/style.css?ver=2.8.3

priority - 38Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 374.5KiB (73% reduction).

Compressing http://zemolezaus.s3.amazonaws.com/wp-content/themes/zemoleza/style.css could save 72.1KiB (85% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ommerce.css?ver=2.1.12 could save 69.1KiB (87% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ftype.min.js?ver=3.9.1 could save 66.3KiB (65% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-includes/js/…y/jquery.js?ver=1.11.0 could save 61.5KiB (65% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ycle2.min.js?ver=2.8.3 could save 14.6KiB (68% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…-layout.css?ver=2.1.12 could save 13.2KiB (87% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…query.jcarousel.min.js could save 12.1KiB (70% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…?ver=3.50.0-2014.02.05 could save 9.9KiB (62% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…s/scripts.js?ver=3.8.1 could save 6.8KiB (71% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…lockUI.min.js?ver=2.60 could save 6KiB (63% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…rk/style.css?ver=2.8.3 could save 5.6KiB (77% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…rd/style.css?ver=2.8.3 could save 5.4KiB (77% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-includes/js/…grate.min.js?ver=1.2.1 could save 4KiB (57% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ls/style.css?ver=2.8.3 could save 4KiB (74% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…lscreen.css?ver=2.1.12 could save 3.6KiB (82% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…lt/style.css?ver=2.8.3 could save 3.4KiB (75% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…complete.css?ver=3.9.1 could save 2.6KiB (67% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ousel.min.js?ver=2.8.3 could save 2.6KiB (62% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…js/client.js?ver=2.8.3 could save 2.5KiB (68% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…ery.maskedinput.min.js could save 1.9KiB (53% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…cart.min.js?ver=2.1.12 could save 1.2KiB (58% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug….tile.min.js?ver=2.8.3 could save 1,003B (51% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ents.min.js?ver=2.1.12 could save 1,002B (62% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…my-login.css?ver=6.3.8 could save 895B (64% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…swipe.min.js?ver=2.8.3 could save 767B (58% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…video.min.js?ver=2.8.3 could save 685B (49% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…ookie.min.js?ver=1.3.1 could save 662B (48% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…rk/script.js?ver=2.8.3 could save 655B (61% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/plug…s/styles.css?ver=3.8.1 could save 634B (57% reduction).

priority - 22Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://s7.addthis.com/js/300/addthis_widget.js (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/plug…avorite-posts/wpfp.css (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…img/bg-noise-verde.jpg (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…oleza/img/bg-noise.jpg (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…visor-icons-header.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…mg/icon-biologicas.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…za/img/icon-exatas.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…/img/icon-facebook.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…img/icon-facebook2.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…a/img/icon-humanas.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…za/img/icon-outras.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…leza/img/icon-plus.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…eza/img/icon-plus2.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…-sociais-aplicadas.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…a/img/icon-twitter.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…/img/icon-twitter2.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…go-zemoleza-footer.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…ogo-zemoleza-index.png (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…query.jcarousel.min.js (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/them…ery.maskedinput.min.js (expiration not specified)
http://zemolezaus.s3.amazonaws.com/wp-content/themes/zemoleza/style.css (expiration not specified)
http://m.addthisedge.com/live/boost?pub=a0a9186bc3…_ate.track.config_resp (60 seconds)
http://s.swiftypecdn.com/cc.js (5 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-KK7SR4 (15 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://js-agent.newrelic.com/nr-974.min.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)

priority - 5Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 45.9KiB (16% reduction).

Compressing http://zemolezaus.s3.amazonaws.com/wp-content/uplo…9/Banner-ze-moleza.jpg could save 23.3KiB (11% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…ogo-zemoleza-index.png could save 5KiB (18% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…go-zemoleza-footer.png could save 4.3KiB (22% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…visor-icons-header.png could save 2.6KiB (95% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…leza/img/icon-plus.png could save 1.4KiB (60% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…mg/icon-biologicas.png could save 1.2KiB (32% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…a/img/icon-humanas.png could save 1.1KiB (28% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…za/img/icon-exatas.png could save 1.1KiB (38% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…za/img/icon-outras.png could save 1.1KiB (34% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…-sociais-aplicadas.png could save 945B (34% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…oleza/img/bg-noise.jpg could save 842B (53% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…img/icon-facebook2.png could save 694B (56% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…a/img/icon-twitter.png could save 684B (34% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…/img/icon-facebook.png could save 636B (41% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…/img/icon-twitter2.png could save 622B (44% reduction).
Compressing http://zemolezaus.s3.amazonaws.com/wp-content/them…eza/img/icon-plus2.png could save 534B (35% reduction).

priority - 2Reduce server response time

priority - 2Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 21KiB (20% reduction).

Minifying http://zemolezaus.s3.amazonaws.com/wp-content/themes/zemoleza/style.css could save 16.2KiB (20% reduction).
Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…rd/style.css?ver=2.8.3 could save 1.4KiB (21% reduction).
Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…rk/style.css?ver=2.8.3 could save 1.4KiB (19% reduction).
Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…ls/style.css?ver=2.8.3 could save 1.2KiB (22% reduction).
Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…lt/style.css?ver=2.8.3 could save 909B (20% reduction).

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 2.9KiB (23% reduction).

Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…s/scripts.js?ver=3.8.1 could save 1.5KiB (16% reduction).
Minifying http://zemolezaus.s3.amazonaws.com/wp-content/plug…js/client.js?ver=2.8.3 could save 1.5KiB (41% reduction).

zemoleza.com.br Mobile Resource Breakdown

Total Resources91
Number of Hosts22
Static Resources34
JavaScript Resources38
CSS Resources13

zemoleza.com.br mobile page usability

Last tested: 2016-10-13


Mobile Usability Bad
64/100

zemoleza.com.br Mobile Usability Test Quick Summary


priority - 36Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

CADASTRE-SE renders only 5 pixels tall (12 CSS pixels).

LOGIN renders only 5 pixels tall (12 CSS pixels).

Tanto os traba…da de pé...rs! and 7 others render only 5 pixels tall (13 CSS pixels).

Procurando TCC…para pesquisa? renders only 7 pixels tall (18 CSS pixels).

No Zé Moleza v…om milhares de and 3 others render only 5 pixels tall (14 CSS pixels).

TCC, monografi…balhos prontos and 2 others render only 5 pixels tall (14 CSS pixels).

+Recentes renders only 6 pixels tall (16 CSS pixels).

+Lidos renders only 6 pixels tall (16 CSS pixels).

+Votados renders only 6 pixels tall (16 CSS pixels).

Todos renders only 6 pixels tall (16 CSS pixels).

Sociais Aplicadas and 8 others render only 7 pixels tall (18 CSS pixels).

(13775) and 8 others render only 6 pixels tall (16 CSS pixels).

Relações Internacionais and 45 others render only 5 pixels tall (14 CSS pixels).

(5290) and 45 others render only 5 pixels tall (14 CSS pixels).

Dicas para mon…alho Acadêmico and 1 others render only 7 pixels tall (18 CSS pixels).

Para não ficar…e de consulta. and 2 others render only 5 pixels tall (14 CSS pixels).

Como fazer Tes…Dissertações? and 4 others render only 6 pixels tall (16 CSS pixels).

Veja o que os…os tem a dizer and 1 others render only 7 pixels tall (18 CSS pixels).

Trabalhos acadêmicos and 2 others render only 8 pixels tall (20 CSS pixels).

O Zé Moleza é…uesa do mundo. and 2 others render only 5 pixels tall (13 CSS pixels).

Nathalia Dutra…Belo Horizonte and 2 others render only 5 pixels tall (13 CSS pixels).
Receba nossos informativos renders only 4 pixels tall (11 CSS pixels).
e fique por de…das novidades renders only 4 pixels tall (11 CSS pixels).
Trabalhos Acadêmicos and 3 others render only 6 pixels tall (16 CSS pixels).
Como fazer Pro…s de Pesquisa? and 14 others render only 5 pixels tall (12 CSS pixels).
O Zé Moleza NÃ…ua monografia. and 2 others render only 5 pixels tall (12 CSS pixels).

priority - 11Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.zemoleza.com.br">Home</a> and 1 others are close to other tap targets.

The tap target <a href="http://zemolez…om.br/humanas/" class="career_title">Humanas</a> and 4 others are close to other tap targets.

The tap target <a href="http://zemolez…administracao/" class="career">Administração</a> and 30 others are close to other tap targets.

The tap target <a href="http://www.zem…como-fazer-tcc">Como fazer TCC?</a> and 4 others are close to other tap targets.

The tap target <a href="http://zemolez…om.br/humanas/">Humanas</a> and 17 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

priority - 3Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 981 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="#box-two" class="box-two">+Recentes</a> falls outside the viewport.

zemoleza.com.br HTML validation

Errors

Legacy doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 98
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "https://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html..."

Bad value “https://www.w3.org/1999/xhtml” for the attribute “xmlns” (only “http://www.w3.org/1999/xhtml” permitted here).

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

Attribute “xmlns:og” not allowed here.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

Attribute “xmlns:fb” not allowed here.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

When the attribute “xml:lang” in no namespace is specified, the element must also have the attribute “lang” present with the same value.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 75 Column: 1 - 77
"...</script> <link rel='https://api.w.org/' href='https://www.zemoleza.com.br/wp-json/' /> <link..."

Bad start tag in “img” in “head”.

Line: 98 Column: 11 - 143
"...<noscript><img height="1" width="1" alt="" style="display:none" src="https://www.facebook.com/tr?id=388695624620651&amp;ev=PixelInitialized" /></nosc..."

Stray end tag “noscript”.

Line: 98 Column: 144 - 154
"...alized" /></noscript> </hea..."

Stray end tag “head”.

Line: 99 Column: 1 - 7
"...noscript> </head> <body..."

Start tag “body” seen but an element of the same type was already open.

Line: 100 Column: 1 - 6
"...> </head> <body> <!-- ..."

No “p” element in scope but a “p” end tag seen.

Line: 207 Column: 1 - 4
"...8230;</p> </p> ..." Line: 212 Column: 1 - 4
"...8230;</p> </p> ..." Line: 217 Column: 1 - 4
"...8230;</p> </p> ..." Line: 222 Column: 1 - 4
"...230;.</p> </p> ..." Line: 227 Column: 1 - 4
"...8230;</p> </p> ..." Line: 232 Column: 1 - 4
"...230;.</p> </p> ..." Line: 241 Column: 1 - 4
"...8230;</p> </p> ..." Line: 246 Column: 1 - 4
"...8230;</p> </p> ..." Line: 251 Column: 1 - 4
"...8230;</p> </p> ..." Line: 256 Column: 1 - 4
"...8230;</p> </p> ..." Line: 261 Column: 1 - 4
"...8230;</p> </p> ..." Line: 266 Column: 1 - 4
"...8230;</p> </p> ..." Line: 275 Column: 1 - 4
"...8230;</p> </p> ..." Line: 280 Column: 1 - 4
"...8230;</p> </p> ..." Line: 285 Column: 1 - 4
"...8230;</p> </p> ..." Line: 290 Column: 1 - 4
"...8230;</p> </p> ..." Line: 295 Column: 1 - 4
"...8230;</p> </p> ..." Line: 300 Column: 1 - 4
"...8230;</p> </p> ..."

Duplicate ID “cse-search-box”.

Line: 389 Column: 45 - 201
"...ontainer'><form action="//www.zemoleza.com.br" id="cse-search-box" method="GET" onsubmit="_gaq.push(['_trackEvent', 'Botoes', 'Buscar', 'Clicou no botao de busca']);"><input..."

Bad value “” for attribute “for” on element “label”: An ID must not be the empty string.

Line: 393 Column: 5 - 18
"...ank"> <label for=""><stron..."

End tag “br”.

Line: 393 Column: 62 - 66
"...s</strong></br>e fiqu..."

Element “span” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 401 Column: 44 - 49
"... class=""><span>Trabal..." Line: 407 Column: 41 - 46
"... class=""><span>Saiba ..." Line: 413 Column: 41 - 46
"... class=""><span>Instit..." Line: 421 Column: 3 - 8
"...redes"> <span>NOSSAS..."

End tag for “body” seen, but there were unclosed elements.

Line: 552 Column: 1 - 7
"...ising --> </body> </htm..."

Unclosed element “div”.

Line: 382 Column: 8 - 31
"... <div class="textwidget"><div s..."

The “for” attribute of the “label” element must refer to a non-hidden form control.

Line: 393 Column: 5 - 18
"...ank"> <label for=""><stron..."

Warnings

Attribute “xmlns” is not serializable as XML 1.0.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

The first occurrence of ID “cse-search-box” was here.

Line: 155 Column: 44 - 200
"...ontainer'><form action="//www.zemoleza.com.br" id="cse-search-box" method="GET" onsubmit="_gaq.push(['_trackEvent', 'Botoes', 'Buscar', 'Clicou no botao de busca']);"><input..."

This document appears to be written in Portuguese. Consider adding “lang="pt"” (or variant) to the “html” start tag.

Line: 2 Column: 99 - 153
"...ml11.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" xmlns:og="https://opengraphprotocol.org/schema/" xmlns:fb="https://www.facebook.com/2008/fbml"> <head..."

zemoleza.com.br similar domains

Similar domains:
www.zemoleza.com
www.zemoleza.net
www.zemoleza.org
www.zemoleza.info
www.zemoleza.biz
www.zemoleza.us
www.zemoleza.mobi
www.emoleza.com.br
www.zemoleza.com.br
www.xemoleza.com.br
www.zxemoleza.com.br
www.xzemoleza.com.br
www.semoleza.com.br
www.zsemoleza.com.br
www.szemoleza.com.br
www.aemoleza.com.br
www.zaemoleza.com.br
www.azemoleza.com.br
www.zmoleza.com.br
www.zwmoleza.com.br
www.zewmoleza.com.br
www.zwemoleza.com.br
www.zsmoleza.com.br
www.zesmoleza.com.br
www.zdmoleza.com.br
www.zedmoleza.com.br
www.zdemoleza.com.br
www.zrmoleza.com.br
www.zermoleza.com.br
www.zremoleza.com.br
www.zeoleza.com.br
www.zenoleza.com.br
www.zemnoleza.com.br
www.zenmoleza.com.br
www.zejoleza.com.br
www.zemjoleza.com.br
www.zejmoleza.com.br
www.zekoleza.com.br
www.zemkoleza.com.br
www.zekmoleza.com.br
www.zemleza.com.br
www.zemileza.com.br
www.zemoileza.com.br
www.zemioleza.com.br
www.zemkleza.com.br
www.zemokleza.com.br
www.zemlleza.com.br
www.zemolleza.com.br
www.zemloleza.com.br
www.zempleza.com.br
www.zemopleza.com.br
www.zempoleza.com.br
www.zemoeza.com.br
www.zemopeza.com.br
www.zemolpeza.com.br
www.zemooeza.com.br
www.zemoloeza.com.br
www.zemooleza.com.br
www.zemokeza.com.br
www.zemolkeza.com.br
www.zemolza.com.br
www.zemolwza.com.br
www.zemolewza.com.br
www.zemolweza.com.br
www.zemolsza.com.br
www.zemolesza.com.br
www.zemolseza.com.br
www.zemoldza.com.br
www.zemoledza.com.br
www.zemoldeza.com.br
www.zemolrza.com.br
www.zemolerza.com.br
www.zemolreza.com.br
www.zemolea.com.br
www.zemolexa.com.br
www.zemolezxa.com.br
www.zemolexza.com.br
www.zemolesa.com.br
www.zemolezsa.com.br
www.zemoleaa.com.br
www.zemolezaa.com.br
www.zemoleaza.com.br
www.zemolez.com.br
www.zemolezq.com.br
www.zemolezaq.com.br
www.zemolezqa.com.br
www.zemolezw.com.br
www.zemolezaw.com.br
www.zemolezwa.com.br
www.zemolezs.com.br
www.zemolezas.com.br
www.zemolezz.com.br
www.zemolezaz.com.br
www.zemolezza.com.br

zemoleza.com.br Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


zemoleza.com.br TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.