Monday, July 4, 2016

Can You Combine Extended Components? AMP-HTML - Not possible

Google Insight will get crazy if you use too many components.
5ouOI.png (2079×1296)
This isn't currently possible. :(

Why gzip Compression Not Detected by PageSpeed Insights

Google's PageSpeed Insights should tell you which resources are not gzipped.
Often they are third party resources out of your control, for example facebook plugins and other resources, or it may be types like SVG that you have not enabled yet.
PageSpeed Insights should be taken as a guide and not gospel.
Don't worry about slowing down website because of 3rd party compressions.
Focus on other critical resources which are actually in your control.

Sunday, June 12, 2016

Download Bulk Page Speed Analysis Software Free

MonitorWebsiteSpeed Tool was developed by Amit for the Windows platform. We are giving away for free to bulk webpage speed testing in real browser.

You can download Bulk MonitorWebsiteSpeed Tool here.

You can select what user agent you would like to test your website speed and also disable images, javascripts, css, flash and popups for finding stuff which may be slowing down your website. Just add list of website and press run. It will create a file on desktop to analyse the page speed further.

Saturday, June 11, 2016

Why add scripts at the bottom of the webpage for improving speed

Most current browsers can download a maximum of two components in parallel for each host name. However, when downloading a script, no other downloads can occur. That download must finish before moving forward.
So, when feasible, it makes perfect sense to move these files to the bottom of your document in order to allow the other components (images, css, etc) to load first.

This is a procedure that we all don't perform enough. Though not always feasible, you can many times speed up your website by placing your script tags next to the closing <body> tag.

How to disable URL rewriting by Google PageSpeed Modules

The PageSpeed modules are open-source server modules for Apache and Nginx that optimize your site automatically. They offer different packages which can be installed on your server. You can download packages here.

By default, all HTML files served by your server and all resources (CSS, images, JavaScript) found in HTML files whose origin matches the HTML file, or whose origin is authorized via Domain, will be rewritten.

However, this can be restricted by using wildcards, using the directives:
ModPagespeedAllow wildcard_spec ModPagespeedDisallow wildcard_spec
pagespeed Allow wildcard_spec;
Disallow wildcard_spec;

These directives are evaluated in sequence for each resource, to determine whether the resource should be consider for rewriting. This is best considered with an example.
Example 1: Excluding JavaScript files that cannot be rewritten
Some JavaScript files are sensitive to their own names as they traverse the DOM. Therefore any rewriting on these files is invalid. We cannot cache-extend them or minifiy them. When such files are identified, we can exclude from the rewriting process via:
ModPagespeedDisallow "*/jquery-ui-1.8.2.custom.min.js"
ModPagespeedDisallow "*/js_tinyMCE.js"


pagespeed Disallow "*/jquery-ui-1.8.2.custom.min.js";
pagespeed Disallow "*/js_tinyMCE.js";

Example2: Specifying explicitly which types of files can be rewritten

If you don't have access to disable it for your site, you can add ?ModPagespeed=off to the end of your URL in the browser like this

Optimizing the Critical Rendering Path for Instant Mobile Websites

Users expect a fast and optimized experience regardless of whether they're on a mobile or desktop browser -- rightfully so! However, delivering instant mobile websites requires careful engineering: you need to account for every extra network roundtrip, tune your servers, and prioritize critical assets -- aka, we need to optimize the critical rendering path to deliver best visual rendering performance.

Here is the video where we'll take a deep dive into the technical design and optimization criteria to help us meet these goals. As a bonus, they have done demo of some existing and upcoming tools they've been working on at Google to automate the process.

How to measure the speed of a website using php?

Simplest way to measure any webpage response time is use Firefox or Chrome developer menu options which display the total access time to the server.

However if you need to do this in PHP then it be done by simple method like below.

 $startTime = microtime(true);

function measureTime(){
global $startTime;
= microtime(true)-$startTime;
"Script execution time: $execTime seconds.";