Profile cover photo
Profile photo
Cindy Krum
Cindy Krum's posts

Post has shared content

Post has shared content
More on HTTPS and HTTP2. WoooooHoooo!!!
We had a fun chat on all things HTTP/2: best practices, server push, HTTPS, websockets, QUIC, and lots more...

Post has shared content
PageSpeed v1.11 (beta) is out with support for Save-Data: - take it out for a spin!

Also, check out this article for great tips on how you can leverage ServiceWorker + Save-Data to reduce data use:

Post has shared content

Post has shared content
An update (March 2016) on the current state & recommendations for JavaScript sites / Progressive Web Apps [1] in Google Search. We occasionally see questions about what JS-based sites can do and still be visible in search, so here's a brief summary for today's state:

# Don't cloak to Googlebot. Use "feature detection" & "progressive enhancement" [2] techniques to make your content available to all users. Avoid redirecting to an "unsupported browser" page. Consider using a polyfill or other safe fallback where needed. The features Googlebot currently doesn't support include Service Workers, the Fetch API, Promises, and requestAnimationFrame.

# Use rel=canonical [3] when serving content from multiple URLs is required.

# Avoid the AJAX-Crawling scheme on new sites. Consider migrating old sites that use this scheme soon. Remember to remove "meta fragment" tags when migrating. Don't use a "meta fragment" tag if the "escaped fragment" URL doesn't serve fully rendered content. [4]

# Avoid using "#" in URLs (outside of "#!"). Googlebot rarely indexes URLs with "#" in them. Use "normal" URLs with path/filename/query-parameters instead, consider using the History API for navigation.

# Use Search Console's Fetch and Render tool [5] to test how Googlebot sees your pages. Note that this tool doesn't support "#!" or "#" URLs.

# Ensure that all required resources (including JavaScript files / frameworks, server responses, 3rd-party APIs, etc) aren't blocked by robots.txt. The Fetch and Render tool will list blocked resources discovered. If resources are uncontrollably blocked by robots.txt (e.g., 3rd-party APIs) or otherwise temporarily unavailable, ensure that your client-side code fails gracefully.

# Limit the number of embedded resources, in particular the number of JavaScript files and server responses required to render your page. A high number of required URLs can result in timeouts & rendering without these resources being available (e.g., some JavaScript files might not be loaded). Use reasonable HTTP caching directives.

# Google supports the use of JavaScript to provide titles, description & robots meta tags, structured data, and other meta-data. When using AMP, the AMP HTML page must be static as required by the spec, but the associated web page can be built using JS/PWA techniques. Remember to use a sitemap file with correct "lastmod" dates for signaling changes on your website.

# Finally, keep in mind that other search engines and web services accessing your content might not support JavaScript at all, or might support a different subset.

Looking at this list, none of these recommendations are completely new & limited to today -- and they'll continue to be valid for foreseeable future. Working with modern JavaScript frameworks for search can be a bit intimidating at first, but they open up some really neat possibilities to make fast & awesome sites!

I hope this was useful! Let me know if I missed anything, or if you need clarifications for any part.

[1] PWA:
[2] Progressive enhancement:
[3] rel=canonical:
[4] AJAX Crawling scheme:

Post has shared content
Legible font size
How to make sure your text is easily readable no matter what device it is being seen on.

Post has shared content
My new blog post: Magnificent Mobile Website And App Analytics: Reports, Metrics, How-to!

As is clear from the graph, mobile rules the world. Yet mobile measurement lags behind. The post above outlines a simple, yet high impact, six step process for mobile site and application measurement.

The data collection mechanisms you need to leverage (tools, tags, tracking), the best reports to start with (standard, custom) and the best metrics to deliver actionable insights (loyalty, app store referrers, micro-outcomes and more).

Mobile friendly sites were important in 2007, we've realize responsive design simply stinks less than the alternative, now it is time to truly step up your measurement game. Here's you plan:

Post has shared content
Responsive images, today!

Great overview video by fellow Googler +Pete LePage 

Post has shared content
Wait while more posts are being loaded