Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Loading...
Seo Master present to you: Cara Optimasi SEO Blog - SEO adalah sebuah tehnik yang sebenarnya adalah bagian dari marketing, sebab dengan tehnik SEO blog bisa mendapatkan pengunjung atau visitor melalui search engine. SEO gampang-gampang susah, karena setiap waktu selalu ada update langsung dari google, itulah yang membuat dan mempengaruhi jika tehnik SEO selalu berubah-ubah.

Cara Optimasi SEO Blog


Berbicara soal SEO, akan lebih baik lagi jika membicarakan tehnik yang simpel namun banyak dilupakan oleh penguna blog. Cara Optimasi SEO Blog, perlu diperhatikan beberapa hal berikut ini:

1. Template

Template ibarat sebuah tampilan rumah, jika templatenya buruk, maka yang dilihat orang ketika mereka melewatinya justru pergi begitu saja. Pilihlah template yang ringan alias SEO friendly, artinya apa, yaitu pilih sebuah template yang jika diakses sangat cepat dan mudah. Dengan demikian, pengunjung akan krasan berada di blog Anda.

2. Pasang Meta Tag

Pasanglah meta tag yang lengkap. Khusus pada meta deskripsi, isilah deskripsi yang lumayan panjang, dan banyak kata kuncinya. Untuk meta keyword, gunakan kalimat yang berubah-ubah tetapi sama. Untuk tehnik lainnya, lengkapi kata kunci rendah dan ringan yang tidak ada saingannya, hal ini juga akan mengoptimasi blog Anda.

3. Nofollow Label

Jangan lupa menjadikan label blogger menjadi nofollow. Karena label tidak mempengaruhi dalam mesin pencari.

4. Backlink

Backlink sangat penting namun juga jangan sampai over untuk memberikan backlink untuk blog Anda. Backlink yang baik adalah backlink yang sesuai dengan niche Anda dan tidak terlalu mengandalkan backlink spam.

Demikianlah Cara Optimasi SEO Blog yang bisa saya tulis, semoga bermanfaat.2013, By: Seo Master

seo Cara Optimasi SEO Blog 2013

Seo Master present to you: By Jacob Moon, Google Developer Programs

If you're a frequent visitor to code.google.com for product updates and reference materials for Google APIs you're working with, you might have noticed that the page loading time (or page rendering time depending on how you see it) has reduced in varying degrees in the past several weeks.

As you'll see below, we've made several changes to help reduce user-perceived latency. This is not an exhaustive list of all improvements we've made recently, but these are the major ones we've made.

As Steve Souders emphasizes as the "Performance Golden Rule" in his book High Performance Web Sites, "only 10-20% of the end user response time is spent downloading the HTML document. The other 80-90% is spent downloading all the components in the page (p.5)".

We agree. That's why we focused our effort on reducing the number and size of downloads (HTTP requests) for the "components" throughout Google Code.
  • Combined and minimized JavaScript and CSS files used throughout the site
Downloading JavaScript and CSS files blocks rendering of the rest of the page. Thus, to reduce the number of HTTP requests made on the initial page load, we combined frequently-used JavaScript and CSS files into one file each. This technique has brought down 20 HTTP requests down to just 2. We also minimized the files by stripping out unnecessary whitespace and shortening function/variable names whenever possible.
  • Implemented CSS sprites for frequently-used images
There are 7 images prominently used throughout Google Code, including the Google Code logo, the googley balls at the bottom of every page, the plus and minus signs as well as the subscribe icon inside each blog gadget.

Although browsers usually download several images in parallel, we concatenated these images into one image so only one HTTP request would be made. Of course, concatenating several images into one required us to make several changes in HTML/CSS. For example, instead of having:

<img src="/images/plus.gif" />


We had to change it to:

<div style="background-image:url(/images/sprites.gif); background-position:-28px -246px; width:9px; height:9px">&amp;</div></span>


where sprites.gif is the concatenated image and background-position and width/height carefully calculated.
  • Implemented lazy loading of Google AJAX APIs loader module (google.load)
We like to eat our own dogfood. Among other APIs, we use our very own AJAX Feed API on product homepages inside the blog gadgets and the AJAX Search API on the search page. These Google AJAX APIs require the Google loader module (google.load) to be loaded first before any of the specific AJAX APIs (i.e. AJAX Feed API, AJAX Search API, Maps API) can be initialized and used. Traditionally, the Google AJAX APIs loader module would be loaded by including the following <script> tag in the <head> section:
    <script type="text/javascript" src="http://www.google.com/jsapi"></script>
This works well in most cases, but when optimizing for the display of static content, this blocks the browser from rendering the rest of the page until it's finished loading that script, thus impacting the user-perceived latency. So instead of loading the Google AJAX APIs loader module upfront, we are now loading it lazily only on the pages where it's required. This is made possible as follows (please note that this is a stripped-down version of what we have on Google Code):

First, in the <head> section, we load the Google AJAX APIs loader module via DOM scripting only on the pages where it's required:

if (needToLoadGoogleAjaxApisLoaderModule) {
    // Load Google AJAX APIs loader module (google.load)
    var script = document.createElement('script');
    script.src = 'http://www.google.com/jsapi?callback=googleLoadCallback';
    script.type = 'text/javascript';
    document.getElementsByTagName('head')[0].appendChild(script);
}
It's important to add the 'callback' parameter in the src attribute, 'callback=googleLoadCallback'. This callback handler will then be called whenever the Google loader module is finished loading.

Then, in the Google loader callback handler (googleLoadCallback()), we initialize the AJAX Feed API and provide the function name that utilizes the AJAX Feed API (startUsingAjaxFeedAPI):
function googleLoadCallback() {
  // Initialize AJAX Feed API
  google.load('feeds', '1', {callback: startUsingAjaxFeedAPI});
}

function startUsingAjaxFeedAPI() {
  // Start using AJAX Feed API
  var feed = new google.feeds.Feed(someFeedUrl);
  ...
}

In effect, we're loading the AJAX Feed API on-demand through the use of two consecutive callback handlers, first to load the Google AJAX APIs loader module (google.load) and then to initialize the AJAX Feed API before it's used. Similar technique can be used for the Maps API and the AJAX Search API.

By now you're probably wondering just how much of an impact did these changes have on Google Code anyways? According to our latency measurement stats, the user-perceived latency on Google Code dropped quite a bit, anywhere between 30% and 70% depending on the page. This is a huge return for relatively small investments we've made along the way, and we hope you'll find these techniques useful for your own web development as well.2013, By: Seo Master

seo How we improved performance on Google Code 2013

Seo Master present to you:

iphone hack: bypass lock screen iOS 6.1

As Apple new iOS 6.1 improved so many features of security but still the glitch was discovered in its supreme security beside this the Google’sandroid mobile operating system has never face such kind of glitches.

                                    iphone hack: bypass lock screen iOS 6.1


The bug of iOS 6.1 is Microsoft exchange bug the device generate excessive communication with Microsoft exchange server this will increase activity of network and drain battery very fast. That is fixed by apple in new release of iOS 6.1.2 for ipad iphone 5 and all iOS 6.1 devices.

The hole in security of iOS 6.1 allow iphone hack by lock screen bypass through which any one can access voice mail, photos, message, and contact and can call. The process does not require any physical access to the hardware of iphone any one can unlock iphone,running iOS 6.1, with in a minute. The process requires only combination and series of button.

STEPS:

     (iphone hack can be done only when iphone is locked)
bypass lock screen iOS 6.1
  1. Unlock iphone by simple sliding.
  2. Press emergency call 
  3. Hold Power button until power down popup shows. Press cancel, the status bar will turn blue. Make emergency call and cancel it as soon as possible so the call does not through.
  4. Press the sleep button to sleep the device then press home button to turn it on.
  5. Unlock the device then press and hold the power button within 3 sec tap emergency call.
  6. Device is ready to use without knowing the password.


In previous iOS, apple faced same security issue that affect devices having iOS 4.1 and can be resolve in iOS 4.2. For now a day’s apple shown lack of urgency to fix the bugs but soon apple will fix the lock screenbypass bug but till then take your phone with you to save your personal data.          


2013, By: Seo Master

seo iphone hack: bypass lock screen iOS 6.1 2013

Powered by Blogger.
Design by Dev Nasser