Archive for maio 11th, 2018

Para a Biologia, para que existem o sexo e os sexos ainda e’ um misterio, que ja foi elucidado pela Matrix/DNA a 30 anos!

sexta-feira, maio 11th, 2018

xxxxx

www.bbc.com/portuguese/geral-43927968

Para que existem o sexo e os sexos? Um dos maiores e mais complicados mistérios da biologia

E desesperador ver as mais destacadas inteligencias dentre humanos dando voltas `as cegas em torno de um fenomeno central que desejam entender, quando a resposta esta’ nas suas costas, para alem da roda e no sentido oposto do objeto. tentam entender o fenomeno da “origem” do sexo, e porque o sexo e’ como e’, buscando as respostas na materia bruta e estupida deste pequeno planeta em que giram dentro do espaco sideral, onde estao as respostas. Se dentro da cosmovisao da Matrix/DNA descobrimos que inclusive astros se reproduzem por mecanismo identico ao sexual, obviamente a resposta nao pode estar aqui (Neste site, na categoria “sexo” tem varios artigos explicativos).

No entanto, registramos o artigo para nos inteirar-mos em que nivel esta’ a obcecada busca… de explicacoes que para nos a 30 anos deixou de ser misterio. E e’ bom lembrar aqui uma das nossas formulas:

Clique na imagem para ampliar

Circuíto Sistêmico ou "Software" extraído da fórmula da Matrix/DNA, Revelando o aspecto Hermafrodita

Circuíto Sistêmico ou “Software” extraído da fórmula da Matrix/DNA, Revelando o aspecto Hermafrodita

 

 

Website: falta o Open Graph para otimizar a Home do site com redes sociais

sexta-feira, maio 11th, 2018

xxxx

The Open Graph protocol

http://ogp.me/

Introduction

The Open Graph protocol enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.

While many different technologies and schemas exist and could be combined together, there isn’t a single technology which provides enough information to richly represent any web page within the social graph. The Open Graph protocol builds on these existing technologies and gives developers one thing to implement. Developer simplicity is a key goal of the Open Graph protocol which has informed many of the technical design decisions.

(ver tiudo)

Me informei sobre Open Graph vendo o seguinte link e texto:

http://www.accessify.com/t/theuniversalmatrix.com

Social Sharing Optimization – poor

Open Graph description is not detected on the main page of The Universal Matrix. 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:

theuniversalmatrix.com open graph image

Website about The Universal Matrix of the Systems and Natural Cycles. Website sobre A Matriz Un…

Source:

<meta property=”og:site_name” content=”The Universal Matrix” />

<meta property=”og:title” content=”The Universal Matrix” />

<meta property=”og:description” content=”Website about The Universal Matrix of the Systems and Natural Cycles. Website so…” />

<meta property=”og:image” content=”http://theuniversalmatrix.com/images/logoIntro.jpg” />

<meta property=”og:type” content=”website” />

<meta property=”og:url” content=”http://theuniversalmatrix.com/” />

 

Website: Importante fonte de dados : Accessify.com

sexta-feira, maio 11th, 2018

xxxx

http://www.accessify.com/t/theuniversalmatrix.com

Dados em junho (o6) dia 11, 2018

Otimo desempenho em loading: apenas 5% dos websites podem carregar mais rapido. Mas porque o Google Analytics esta tomando 25% do tempo de carregamento? Ver ou deletar Google analytics? 

  • First response

    235 ms

    Resources loaded

    387 ms

    Page rendered

    119 ms

    Total page load time

    741 ms

  • Welcome to theuniversalmatrix.com homepage info – get ready to check The Universal Matrix best content for Brazil right away, or after learning these important things about theuniversalmatrix.com

    We analyzed Theuniversalmatrix.com page load time and found that the first response time was 235 ms and then it took 506 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

  • Page load speed analysis
    • 83/100

      Good result

    • 5

      Successful tests

    • 3

      Failed tests

Our browser made a total of 8 requests to load all elements on the main page. We found that 75% of them (6 requests) were addressed to the original Theuniversalmatrix.com, 25% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (235 ms) belongs to the original domain Theuniversalmatrix.com.

Name
Timeline

xxxx

Page optimization ( O javascripts toma 43.1 kb dos 56.0 kb do website, o que torna mais lento o carregamento. Sera que o problema das mensagens de “scripts inseguros” esta vindo disso?

  • HTML 2.2 kB
    Images 10.2 kB
    Javascripts 43.1 kB
    CSS 467 B

In fact, the total size of Theuniversalmatrix.com main page is 56.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 43.1 kB which makes up the majority of the site volume.

Ver isto tambem sobre JavaScript:

JavaScript optimization

  • Original – 43.1 kB
  • After minification – 43.1 kB
  • After compression – 16.0 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 27.1 kB or 63% of the original size

xxxxxx

DNS record:

Type Host Target/ip TTL Other
A theuniversalmatrix.com 107.161.189.66 14400
NS theuniversalmatrix.com ns08.hmnoc.net 86400
NS theuniversalmatrix.com ns07.hmnoc.net 86400
SOA theuniversalmatrix.com 86400 Mname: ns07.hmnoc.net
Rname: whm.hostmach.com.br
Serial: 2017020700
Refresh: 86400
Retry: 7200
Expire: 3600000
Minimum-ttl: 86400
MX theuniversalmatrix.com theuniversalmatrix.com 14400 Pri: 10
TXT theuniversalmatrix.com 14400 Txt: v=spf1 +a +mx +ip4:107.161.189.66 ~all

xxxxxxx

HTML optimization

  • Original – 2.2 kB
  • After minification – 2.2 kB
  • After compression – 1.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 1.2 kB or 53% of the original size.

Image optimization

  • Original – 10.2 kB
  • After optimization – 10.2 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. The Universal Matrix images are well optimized though.

CSS optimization

  • Original – 467 B
  • After minification – 362 B
  • After compression – 229 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. Theuniversalmatrix.com needs all CSS files to be minified and compressed as it can save up to 238 B or 51% of the original size.

xxxx

Importante: Falta o Open Graph na homepage para otimizar conexao com redes sociais

Social Sharing Optimization : Poor result

Open Graph description is not detected on the main page of The Universal Matrix. 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:

Website: Mudanca de Http para Https. O que fazer?

sexta-feira, maio 11th, 2018

xxxx

Obtido no site do Mozilla:

https://infosec.mozilla.org/guidelines/web_security#http-redirections

Websites may continue to listen on port 80 (HTTP) so that users do not get connection errors when typing a URL into their address bar, as browsers currently connect via HTTP for their initial request. Sites that listen on port 80 should only redirect to the same resource on HTTPS. Once the redirection has occured, HSTS should ensure that all future attempts go to the site via HTTP are instead sent directly to the secure site. APIs or websites not intended for public consumption should disable the use of HTTP entirely.

Aviso obtido em:

http://www.accessify.com/t/theuniversalmatrix.com

HTTPS certificate

SSL Certificate

Theuniversalmatrix.com has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

xxxx

Ajuda/instrucao do GOOGLE para mudar para https:

https://support.google.com/webmasters/answer/6073543

Secure your site with HTTPS

Protect your site and your users

What is HTTPS?

HTTPS (Hypertext Transfer Protocol Secure) is an internet communication protocol that protects the integrity and confidentiality of data between the user’s computer and the site. Users expect a secure and private online experience when using a website. We encourage you to adopt HTTPS in order to protect your users’ connections to your website, regardless of the content on the site.

Data sent using HTTPS is secured via Transport Layer Security protocol (TLS), which provides three key layers of protection:

  1. Encryption—encrypting the exchanged data to keep it secure from eavesdroppers. That means that while the user is browsing a website, nobody can “listen” to their conversations, track their activities across multiple pages, or steal their information.
  2. Data integrity—data cannot be modified or corrupted during transfer, intentionally or otherwise, without being detected.
  3. Authentication—proves that your users communicate with the intended website. It protects against man-in-the-middle attacks and builds user trust, which translates into other business benefits.

Best practices when implementing HTTPS

Use robust security certificates

You must obtain a security certificate as a part of enabling HTTPS for your site. The certificate is issued by a certificate authority (CA), which takes steps to verify that your web address actually belongs to your organization, thus protecting your customers from man-in-the-middle attacks. When setting up your certificate, ensure a high level of security by choosing a 2048-bit key. If you already have a certificate with a weaker key (1024-bit), upgrade it to 2048 bits. When choosing your site certificate, keep in mind the following:

  • Get your certificate from a reliable CA that offers technical support.
  • Decide the kind of certificate you need:
    • Single certificate for single secure origin (e.g. www.example.com).
    • Multi-domain certificate for multiple well-known secure origins (e.g. www.example.com, cdn.example.com, example.co.uk).
    • Wildcard certificate for a secure origin with many dynamic subdomains (e.g. a.example.com, b.example.com).

Use server-side 301 redirects

Redirect your users and search engines to the HTTPS page or resource with server-side 301 HTTP redirects.

Verify that your HTTPS pages can be crawled and indexed by Google

  • Do not block your HTTPS pages by robots.txt files.
  • Do not include meta noindex tags in your HTTPS pages.
  • Use Fetch as Google to test that Googlebot can access your pages.

Support HSTS

We recommend that HTTPS sites support HSTS (HTTP Strict Transport Security). HSTS tells the browser to request HTTPS pages automatically, even if the user enters http in the browser location bar. It also tells Google to serve secure URLs in the search results. All this minimizes the risk of serving unsecured content to your users.

To support HSTS, use a web server that supports it and enable the functionality.

Although it is more secure, HSTS adds complexity to your rollback strategy. We recommend enabling HSTS this way:

  1. Roll out your HTTPS pages without HSTS first.
  2. Start sending HSTS headers with a short max-age. Monitor your traffic both from users and other clients, and also dependents’ performance, such as ads.
  3. Slowly increase the HSTS max-age.
  4. If HSTS doesn’t affect your users and search engines negatively, you can, if you wish, ask your site to be added to the HSTS preload list used by most major browsers.

Consider using HSTS preloading

If you enable HSTS, you can optionally support HSTS preloading for extra security and improved performance. To enable preloading, you must visit hstspreload.org and follow the submission requirements for your site.

Avoid these common pitfalls

Throughout the process of making your site secure with TLS, avoid the following mistakes:

Issue Action
Expired certificates Make sure your certificate is always up to date.
Certificate registered to incorrect website name Check that you have obtained a certificate for all host names that your site serves. For example, if your certificate only covers www.example.com, a visitor who loads your site using just example.com (without the “www.” prefix) will be blocked by a certificate name mismatch error.
Missing Server name indication (SNI) support Make sure your web server supports SNI and that your audience uses supported browsers, generally. While SNI is supported by all modern browsers, you’ll need a dedicated IP if you need to support older browsers.
Crawling issues Don’t block your HTTPS site from crawling using robots.txt.
Indexing issues Allow indexing of your pages by search engines where possible. Avoid the noindex meta tag.
Old protocol versions Old protocol versions are vulnerable; make sure you have the latest and newest versions of TLS libraries and implement the newest protocol versions.
Mixed security elements Embed only HTTPS content on HTTPS pages.
Different content on HTTP and HTTPS Make sure the content on your HTTP site and your HTTPS is the same.
HTTP status code errors on HTTPS Check that your website returns the correct HTTP status code. For instance 200 OK for accessible pages, or 404 or 410 for pages that do not exist.

More tips

See the HTTPS migration FAQs for more tips about using HTTPS pages on your site.

Migrating from HTTP to HTTPS

If you migrate your site from HTTP to HTTPS, Google treats this as a site move with a URL change. This can temporarily affect some of your traffic numbers. See the site move overview page to learn more.

Add the HTTPS property to Search Console; Search Console treats HTTP and HTTPS separately; data for these properties is not shared in Search Console. So if you have pages in both protocols, you must have a separate Search Console property for each one.

More information

More details on implementing TLS on your site:

xxxxx

https://stackoverflow.com/questions/4083221/how-to-redirect-all-http-requests-to-https

How to redirect all HTTP requests to HTTPS