domstat.net

Website loading time

during the test: 1.77 s

cable connection (average): 2.05 s

DSL connection (average): 2.34 s

modem (average): 17.28 s

HTTP headers

HTTP/1.0 200 OK

Content-Type: text/html; charset=UTF-8

Expires: Sun, 16 Oct 2011 00:15:22 GMT

Date: Sun, 16 Oct 2011 00:15:22 GMT

Cache-Control: private, max-age=0

Last-Modified: Sat, 30 Jul 2011 22:38:12 GMT

ETag: "72044fc0-4d76-416a-af4a-4a90a6880cd4"

X-Content-Type-Options: nosniff

X-XSS-Protection: 1; mode=block

Server: GSE

Information about DNS servers

Received from the first DNS server

Request to the server "google-code-updates.blogspot.com"
You used the following DNS server:
DNS Name: shades03.rzone.de
DNS Server Address: 85.214.0.233#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 42641
flag: qr rd REQUEST: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

REQUEST SECTION:
google-code-updates.blogspot.com. IN ANY

Received 50 bytes from address 85.214.0.233#53 in 100 ms

Received from the second DNS server

Request to the server "google-code-updates.blogspot.com"
You used the following DNS server:
DNS Name: docks05.rzone.de
DNS Server Address: 81.169.146.15#53
DNS server aliases:

HEADER opcode: REQUEST, status: NOERROR, id: 63340
flag: qr rd REQUEST: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

REQUEST SECTION:
google-code-updates.blogspot.com. IN ANY

Received 50 bytes from address 81.169.146.15#53 in 89 ms

Subdomains (the first 50)

Typos (misspells)

Location

IP: 209.85.175.132

continent: NA, country: United States (USA), city: Mountain View

Website value

rank in the traffic statistics:

There is not enough data to estimate website value.

Basic information

website build using CSS

code weight: 108.57 KB

text per all code ratio: 29 %

title: The Google Code Blog

description:

keywords:

encoding: UTF-8

language: en

Website code analysis

one word phrases repeated minimum three times

two word phrases repeated minimum three times

three word phrases repeated minimum three times

B tags

From lightning talks in Mountain View, to App Engine hackathons in Tokyo, to lectures in Berlin, the GTUGs are a great place to meet fellow developers and learn (or teach) something new.At Google I/O, there were many folks eager to bring the spirit of the conference back to their hometowns by starting up GTUGs of their own. Since the conference ended, our list of current GTUGs has grown to include this 'baby boomer' generation of chapters. The following are all new groups looking for members and starting to set up their first events.If there's one near you, check it out! Let the organizers know you're interested; suggest topics for discussion and even offer to do a talk about your own experiences.Europe

Paris GTUG - http://groups.google.com/group/paris-gtugHamburg GTUG - http://www.hamburg-gtug.orgGTUG Munich - http://gtug-muc.orgIstanbul GTUG - http://www.istanbul-gtug.org/Polish GTUG - http://www.gtug.plNorth America

Tri-Valley California GTUG - http://groups.google.com/group/tv-gtugBerkeley GTUG - http://www.meetup.com/Berkeley-GTUG/San Diego GTUG - http://www.meetup.com/sd-gtug/NYC GTUG - http://sites.google.com/site/nycgtugNew Jersey GTUG - http://nj-gtug.org/Philly/Delaware GTUG - http://sites.google.com/site/phillygtug/Boston GTUG - http://groups.google.com/group/boston-gtugDenver GTUG - http://groups.google.com/group/denver-gtugTwin Cities GTUG - tc-gtug.orgAustin GTUG - http://sites.google.com/site/austingtug/Michigan GTUG - http://groups.google.com/group/mi-gtugMadGTUG - http://madgtug.orgCleveland GTUG - http://groups.google.com/group/cleveland-gtugUtah GTUG - http://utahgtug.blogspot.com/Laguna GTUG - www.laguna-gtug.orgQuebec GTUG - http://groups.google.com/group/gtug-quebec/?pli=1South America

Chile GTUG - http://groups.google.com/group/gtug-clArgentina GTUG - http://groups.google.com/group/gtug-arAsia

Optimizing Database Performance

There are hundreds of books written about optimizing SQL and database performance, so I won't bother to get into these details, but instead focus on things which are of particular interest for mobile HTML5 apps.Problem: Creating and deleting tables is slow!

Solution: Smart versioning and backwards compatible schema changes (whenever possible).

Problem: Queries are slow!

Solution: Defer and/or combine queries.

SELECT Author, COUNT(*) as NumArticlesFROM MagazinesGROUP BY AuthorORDER BY NumArticles;SELECT Author, COUNT(*) as NumBooksFROM BooksGROUP BY AuthorORDER BY NumBooks;This will work fine, but the additional query will generally cost you about 100-200 ms over a different (albeit less pretty) query like:SELECT Author, NumPublications, PubTypeFROM ( SELECT Author, COUNT(*) as NumPublications, 'Magazine' as PubType, 0 as SortIndex FROM Magazines GROUP BY Author UNION SELECT Author, COUNT(*) as NumPublications, 'Book' as PubType, 1 as SortIndex FROM Books GROUP BY Author)ORDER BY SortIndex, NumPublications;This will return all the entries we want, with the magazine entries first in increasing order of number of articles, followed by the book entries, in increasing order of the number of books. This is a toy example and there are clearly other ways of improving this, such as merging the Magazines and Books tables, but this type of scenario shows up all the time. There's always a trade-off between simplicity and speed when dealing with databases, but in the case of HTML5 on mobile, this trade-off is even more important.Problem: Multiple updates is slow!

Solution: Use Triggers whenever possible.

CREATE TRIGGER IF NOT EXISTS RemoveAuthorAFTER DELETE ON BooksBEGIN DELETE FROM Authors WHERE Author NOT IN (SELECT Author FROM Books);END;We'll get into more detail on triggers and how to use them in another performance post to come.Optimizing AppCache Performance

Problem: Logging in is slow!

Solution: Avoid redirects to the login page. App-Cache is great because it can launch the application without needing to hit the network, which makes it much faster and allows you to launch offline. One problem you might encounter though, is that the application will launch and then you'll need to hit the network to get some data for the current user. At this point you'll have to check that the user is authenticated and it might turn out that they're not (e.g., their cookies might have expired or have been deleted). One option is to redirect the user to a login page somewhere, allow him to authenticate and then redirect him back to the application. Regardless of whether or not the login page is listed in the manifest, when it redirects back to your application, the entire application will reload. A nicer approach is for the application itself to display an authentication interface which sends the credentials and does the authentication seamlessly in the background. This will avoid any additional reloads of the application and makes everything feel faster and better integrated.Problem: AppCache reloading causes my app to be slow!

Solution: List as few URLs in the manifest as possible.

U tags

I tags

Posted by Mike Marchak, Google Code Team

images

headers

H1

Google Code Blog

H2

Monday, June 22, 2009

Thursday, June 11, 2009

Wednesday, June 10, 2009

Tuesday, June 9, 2009

Archives

H3

Monday, June 22, 2009

Thursday, June 11, 2009

Wednesday, June 10, 2009

Tuesday, June 9, 2009

Archives

H4

H5

H6

internal links

external links