What is “Security Issues” in GWT?
10 years ago
Click on the Security Issues tab on the side bar of GWT.
The Security Issues pages lets you know of any known security issues with your site. If you visit your website and get a malware warning from your browser, it is likely that your website is referencing code or content from another website that has malware.
If your site has been hacked or compromised, the search results of your website on Google will show up with “This site may harm your computer.” Or “This site may be hacked.” This will avoid people from visiting your website. It is important to check the Security Issues tab regularly to see whether Google has marked your site as being hacked.
There are numerous things that can cause your site to be compromised such as: server configuration, SQL injection, code injection, error template, binary malware, content injection and URL injection. One way to address these issues is by locating the problematic content and removing it.
Filed under: Documentation→Website Performance
Tags: google webmaster tools, gwt, hackers, malware, security issues, sql injection, url injection, website performance
How to analyze my webpage using Google PageSpeed?
10 years ago
To analyze your webpage online using Google PageSpeed you can go to:
https://developers.google.com/speed/pagespeed/insights/
You can also analyze your webpage from your Chrome browser by downloading the plugin:
https://chrome.google.com/webstore/detail/pagespeed-insights-by-goo/gplegfbjlmmehdoakndmohflojccocli?hl=en
After installing the plugin, you can analyze a page by going to your browser’s customize and control dropdown menu. Go to “More tools” and click on “Developer tools”.
Click on “Pagespeed” tab at the top of the developer tools and click on “Analyze” to analyze the page you’re on.
Filed under: Documentation→Website Performance
Tags: analyze webpage, google pagespeed, pagespeed insights, website performance
Why you should avoid and minimize redirects
10 years ago
To increase your page speed, you should try your best to avoid or minimize redirects on your website. If a mobile user goes to example.com and it redirects them to www.example.com then redirects them to m.example.com, the user will experience slow page loads. Having a landing page that redirects multiple times to the final landing page will slow your page speed. Instead, you can design your website so that example.com uses a responsive design with different break points for desktops, tablets and mobile devices.
Filed under: Documentation→Website Performance
Tags: avoid redirects, minimize redirects, page speed, redirects, website performance
Why you should enable compression
10 years ago
To increase your page speed, you should enable some sort of compression for your website. Most modern browsers support gzip compression. Enabling compression will reduce the size transferred response by up to 90%, reduce the client’s data usage and improve the time to render your pages.
It is recommended to enable text compression with GZIP on your web server.
Filed under: Documentation→Website Performance
Tags: enable compression, GZIP, page speed, website performance
Why you should improve your server response time
10 years ago
There are many potential factors that may slow down the response time of your server. Some causes could be slow application logic, slow database queries, slow routing, frameworks, libraries, resource CPU starvation or memory starvation.
If you believe your slow response time is due to CPU or memory, you may think about upgrading your web server. It is important to reduce your server response time to less than 200ms.
Filed under: Documentation→Website Performance
Tags: page speed, server response time, website performance
Why you should leverage browser caching
10 years ago
Fetching resources between the client and server can be very slow and expensive for the visitor. To increase your page speed, you should always consider using caching to help determine whether the browser can reuse a previously fetched resource.
Filed under: Documentation→Website Performance
Tags: browser caching, page speed, website performance
Why you should minify resources when you can
10 years ago
Minifying resources is when you remove unnecessary or redundant data without affecting how the page is shown by the browser. For instance, you can create a header.php page and include it to all your pages instead of having duplicates of the header on every page. You can also remove comments in your code, remove unused code and use shorter variables and function names to improve your page speed.
Filed under: Documentation→Website Performance
Tags: minified, minify, minifying resources, page speed, website performance
Why you should optimize all images on your website
10 years ago
Images usually account for the most bytes on a page. Therefore, it is very important for you to optimize your images. The less bytes the images are, the faster your pages will load up. Using the right image optimization is a process you need to take. Be careful when optimizing your images. If you optimize the images too much, the quality of the images may be poor. Also be on the lookout for images that you can replace with CSS effects or web fonts. Any image that you can eliminate or replace with web fonts or CSS effects will help with your page speed.
Filed under: Documentation→Website Performance
Tags: CSS effects, optimize images, page speed, web fonts, website performance
Why you should optimize CSS delivery
10 years ago
Browsers will block rendering a page until all external style sheets are downloaded and processed. It is vital to optimize your CSS delivery so that your page can load faster. You can do so by inlining small CSS files directly into your HTML document. Do not inline large data URIs or CSS attributes.
Filed under: Documentation→Website Performance
Tags: CSS delivery, optimize CSS, page speed, website performance
Why you should prioritize visible content on your pages
10 years ago
To increase your page speed, try to reduce the size of the above-the-fold content. The above-the-fold content is implying the upper half of the front page of your website that doesn’t require you to scroll down the page to see. Many websites that seem very fast are often just as large as slow websites. They just prioritize the above the fold content so that the site appears to load fast. Users love webpages that show up quickly and this is why you should prioritize visible content on your pages. Always load the above the fold content first. The footer is at the bottom of the page for a reason so it doesn’t make any sense to add many external files or images to your footer. The user will rarely see your footer. Structure your HTML so that it loads the critical above-the-fold content first and reduce the amount of data used by your resources.
Filed under: Documentation→Website Performance
Tags: above-the-fold, page speed, prioritize visible content, website performance