If you want to increase your website speed and performance then this article will help you to make it fix by using GTMetrix. What is GTMetrix? GTmetrix is a free tool that analyzes your website loading time and page speed by using Google Page speed score and YSlow score.
With to help of WordPress free plugin we will reduce the page load time also reduce your page size. So, Lets get in to it.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Now you have to go to ‘Settings‘. When you hover on settings then you will see ‘ShortPixel Al‘ in the list, click on it.
Now two tabs will appear on the screen ‘General‘ and ‘Advanced‘. You don’t need to change anything in the rest tabs.
Go to the ‘General’ Setting tab and make sure that all the setup is configured properly like the compression level should be ‘Lossless’ and WebP support ‘Checked’ and Fade-in effect ‘Checked’. Then click on Save Changes.
Go to the ‘Advanced’ tab. ‘API URL’ will be remain the same as configured automatically. Replace method ‘SRC’ & ‘Excluded URLs‘ should be the same as per default settings.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Shortpixel Al Advance Settings
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Now click on ‘Save Changes’ don’t do anything else. The API URL of the ShortPixel Al will take your images data and optimize your website images automatically.
Go to GTMetrix again type your domain URL and execute the test of page speed. This time you will observe that your Serve Scale Images error fixed and it reduce the time of page load and performance at the same time.
[et_pb_section fb_built=”1″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]The biggest factor contributing to the success of any business’ website is user experience (UX). A crucial element of UX is a fast-responding website. So how to improve your website?
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Research indicates that 47% of web users expect a web page to load in under two seconds. Moreover, 40% of web users leave a website if it takes longer than three seconds to load. And even a second delay in web page response times can cause a 7% drop in conversions.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Page load speed directly affects customer engagement, conversion rates, SEO, and brand promotion. Choosing the right web hosting provider and service plan will optimize website performance.
Uncompressed web page files such as Cascading Style Sheets (CSS) and Javascript (JS) files can slow page load times. Large, unoptimized image files also impede web page load speeds.
Many eCommerce websites use third party scripts for cookies, advertising, analytics, social networking, and apps. Delays in load times occur when a browser detects a third-party script, loading data from multiple databases sourced from hidden party servers. Thus, it’s best to keep third-party services to a minimum.
Another means to improve a website’s load times is to enable browser caching. This will improve response times for returning visitors.
[/et_pb_text][et_pb_image src=”https://blog.gotmenow.com/wp-content/uploads/2021/09/website-performance-measurement.jpg” alt=”improve your website speed” title_text=”improve your website speed” align=”center” _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_image][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Does The Hosting Provider Offer A Contact Delivery Network (CDN)?
To optimize load speeds to users worldwide, ensure the web hosting provider offers contact delivery networks (CDNs). Without the benefit of a CDN, a website’s content is sourced from just one server serving global visitors from all continents.
For example, if a visitor from New Zealand accesses content hosted on an origin server in Europe, inevitably, response times will lag. A worldwide CDN has points-of-presence (POPs) spread around the globe, routing website requests to the nearest CDN POP. Reducing the physical distance between a responding server and a requesting location greatly decreases load and response times.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]A CDN is vital to optimizing worldwide UX. Researchers have found that, on average, a CDN slashes website lag (latency) by 83% compared to websites without a CDN.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Web Hosting Plans Matter
The type of web hosting plan a business uses will impact user response times and UX. A shared hosting plan, while the least expensive option, is also the least robust in terms of performance, security, and flexibility.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]A shared hosting server accommodates multiple websites, all of which share the server’s resources such as available bandwidth, CPU, RAM, and memory. If a website suffers from slow web page loads and response times, the first step is to upgrade to a more powerful hosting solution.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Dedicated server hosting will greatly improve website performance. However, this option comes at a relatively high cost. A more economical choice is a virtual private server (VPS) solution, which delivers most of the advantages of a dedicated server.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
When considering web host providers, part of one’s due diligence is to evaluate the storage devices they use. Find out if their servers deploy solid-state drives (SSDs). Faster and more reliable than legacy hard disk drives (HDDs), SSDs achieve greater speed through more efficient data throughput and much faster seek times. Moreover, SSDs are an eco-friendly choice as they use less energy than HDDs.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]What web server software does the hosting provider use? While Apache HTTP is widely used across multiple computing platforms, some hosting providers now rely on faster technologies such LiteSpeed Web Server (LSWS) or Nginx.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Another important consideration is the web host’s relational database management system (RDMS). The most popular DB engine is Oracle’s MySQL but the MariaDB RDMS-a variant of MySQL-delivers faster performance.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Free online tools are available to test a website’s speed. Use Google’s PageSpeed Insights or the Pingdom Web Site Speed Test to determine any possible chokepoints. These tests grade websites and note what elements can be improved.
[et_pb_section fb_built=”1″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]A fast website is crucial in maintaining a positive user experience. Evidence suggests that users become distracted if there is even a one-second delay. Every second after that increases the likelihood the end-user will leave. This is why it’s imperative your website loads quickly. This article will briefly address a number of methods that you can use to speed up your website loading time.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default” custom_margin=”5px|auto||auto||”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
1. Reduce File Sizes
The amount of content that can be delivered in a discrete amount of time is limited by a finite amount of bandwidth. All things being equal, the larger the files on a site, the longer it takes for them to load. While large file sizes may not have much of an impact on users who use extremely high-speed connections (such as T1 or T3 connections), it will impact those running on slower hookups.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]The best way to reduce file sizes is to run your images through various optimization techniques. Some techniques include:
Compressing images via tools such as Photoshop and/or Compress PNG. There are several image compression tools out there that make it simple to make files smaller.
Resizing your image so it’s smaller. The smaller it is, the faster it loads.
Picking a file type appropriate for your image. Typically, you’ll choose between JPEG, GIF, and PNG. JPEG is great for quality in a small size, GIFs should only be used for thumbnails and as decorative images, and PNGs are excellent because their quality won’t degrade with re-saves.
Sometimes, you might need to consider eliminating some files. The less your website has to load, the better.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
After reducing file sizes, compress images on the server using HTTP compression. This will reduce the amount of bandwidth required to load content, thus improving the speed of your website.
One way you can compress files is with Gzip compressing. Gzip can compress HTML, JavasScript, XML, CSS, fonts, and just about anything you render on your site. Gzipping can be enabled on an Apache server using the mod_deflate module in your root .htaccess file and adding a filter for each file type that your site delivers.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
3. Caching For Improving Website Loading Time
If a website requires a webpage load every time there is a unique visit, then every file that you have on the page needs to be downloaded individually. This includes everything from the HTML, CSS, JavaScript, and any other assets your site provides. This can lead to slow load times for a particular webpage.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]The best way to prevent this is to use the caching function most browsers have built-in. Doing so will speed up the response time of a page on subsequent visits.
In addition to this, you can let browsers know to serve a cached version of a webpage by adding Expires Headers. These headers tell the browser which content is static and which content is dynamic. This is a great option to cut some of the load time for repeat visitors.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Too many calls to the server can lead to significant slowdowns of your website. Sending any request to a server requires full communication, including a request and response, before the page can be rendered. To increase website loading speed.
Here are a number of ways you can reduce HTTP calls.
[/et_pb_text][et_pb_image src=”https://blog.gotmenow.com/wp-content/uploads/2021/09/guest-blogging-websites.jpeg” alt=”website loading time” title_text=”website loading time” _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_image][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Use CSS Image Sprites
Creating CSS image sprites is one easy way to reduce the number of server calls your website receives. Instead of loading 20 individual images to a site, sprites load one large image containing all the necessary elements in it so it can be zeroed in using CSS.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Reduce Your HTTP Redirects
If several 3xx response codes appear on your website, you are likely sending users to get information from too many locations. Avoid doing this, even if it is for SEO purposes.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Fix Broken Links to Files
Anytime your site sends instructions to a server to look for a file that doesn’t exist, a 404 error will appear. Too many 404s can increase your page load time.
Take the time to fix any 404s you come across. Doing so will significantly improve your website and website loading speed.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
5. Optimize Your Dynamic Content to Improve Website Loading Time
Minify
While a blank space within CSS and JavaScript files may appear to be empty to the human eye, each blank character must be read and processed by the browser engine. In cases such as these, make sure to minify by reducing the number of blank characters in files. Doing so will decrease the amount of time it takes a web browser to render content.
There are several free tools you can use to minify your files:
Some sites automatically convert HTML into an in-site scripting language. As you can imagine, the time it takes to convert HTML can slow down your website. It’s better for your website if your content is delivered as raw HTML.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
CSS at the Top/JavaScript at the Bottom
CSS should be placed near the top of your page. This ensures the page loads right away and is rendered properly.
JavaScript can take a while to load, so you want it near the bottom of the page. This way it runs after the rest of the page loads. With CSS near the top, this will make sure users at least have content while the rest of the webpage loads.
If you are using a small amount of JavaScript, avoid calling it in a separate file. Instead, to reduce HTTP requests, include JavaScript code directly on the page.
Note: if you intend to use any popular JavaScript libraries, use a CDN to deliver your content to take advantage of the fact that many people will already have these downloaded in their browser caches. This will significantly reduce page load time.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Writing well-designed query database calls can have a significant impact on the time it takes for content to be delivered to your site. Poorly written queries can have a pronounced negative effect on page load time. This is particularly true for sites that have quite a bit of traffic and/or deliver a large number of products.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]While database optimization is a large topic, here are a few quick tips.
One of the most common mistakes made by developers is to use a wildcard query to retrieve results. Take, for instance:
“select * from table_name”
A large table can slow you down quite a bit. If you don’t need every field, request individual keys from the table, like so:
“select field1, field2 from table_name”
Other ways you can improve performance include making sure that the database is properly indexed, reducing correlated subqueries, and avoiding temporary tables.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
7. Hosting Provider
A website is only as fast as its weakest link, so choosing a good web provider and plan may prove to be a crucial factor in delivering your site at optimum speeds. If you’re using large central providers such as AWS, you may wish to use Content Delivery Networks (CDNs).
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
8. Use a CDN to Reduce Latency
Physical distance from the server can increase the time it takes for a server to respond to an HTTP request. By using CDNs, you can place servers in different locations around the globe, which will reduce load times for people in different regions.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Final Notes
This is only a small sampling of different techniques one can use to speed up a website. Each one could easily be covered in more detail. However, you may wish to use this piece as a checklist of techniques you can try if your site has slow response times.
Not sure if your website is running slow? That’s where Airbrake’s Performance Monitoring comes in. Our developer-centric Performance Monitoring software gives you the tools you need to make sure your app or website is running smoothly and quickly. With Performance Monitoring, you’ll have access to requests and response times, Apdex Score, error occurrences, and so much more. Try Airbrake Performance Monitoring today with a free 30-day trial where you’ll get unlimited performance events, error monitoring, unlimited users, and unlimited projects.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_post_slider posts_number=”8″ include_categories=”2″ bg_overlay_color=”#0C71C3″ _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_post_slider][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_social_media_follow _builder_version=”4.9.10″ _module_preset=”default” text_orientation=”center”][et_pb_social_media_follow_network social_network=”facebook” url=”https://www.facebook.com/Gotmenownrp” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#3b5998″ follow_button=”off” url_new_window=”on”]facebook[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”twitter” url=”https://twitter.com/Gotmenow3″ _builder_version=”4.9.10″ _module_preset=”default” background_color=”#00aced” follow_button=”off” url_new_window=”on”]twitter[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”linkedin” url=”https://www.linkedin.com/in/gotmenow-soft-solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#007bb6″ follow_button=”off” url_new_window=”on”]linkedin[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”instagram” url=”https://www.instagram.com/gotmenow_soft_solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#ea2c59″ follow_button=”off” url_new_window=”on”]instagram[/et_pb_social_media_follow_network][/et_pb_social_media_follow][/et_pb_column][/et_pb_row][/et_pb_section]
Website speed is much important now a days. And check here in this article how to improve the website speed of your site.
Page loading speed is more vital now than it’s ever been, as the rising number of mobile devices makes a speedy site not just “nice to have” but absolutely essential.
Page load speed has always been an important consideration when creating websites. But as more consumers are spending time researching products and services on mobile devices, they want to be able to complete tasks and make purchases quickly. A fast site is a key part of that. But how fast does your website need to be? And what’s the impact on your bottom line? In this article, we look at these questions and try to find some answers with our deep dive into website speed.
First, let’s cover the basics. When we talk about website speed, we’re really talking about load time, which is how quickly you can get the information on your server rendered correctly on a user’s device. Load times are measured in seconds and milliseconds. According to Google, if pages have a loading time of more than one second it damages the user experience. Google admits that a sub-one second page load time is a massive goal, and the variety of network types and speeds for accessing mobile content makes the issue more acute.
Before you can improve your site’s load time, you need to establish how fast it actually is. Fortunately, there are free tools available that help with this. Google Developers offers a website tool that includes information about where your site speed is good or bad, broken out between mobile and desktop. Just plug in your URL and you get a quick assessment of how your site loads both on mobile and desktop interfaces.
It uses a simple traffic light system so you can see how your site is doing and provides recommendations for areas you should fix or should consider fixing. Along with this, you get a snapshot of how your site will look on a typical mobile device, which allows you to address areas like menus and logos that take up too much space. Google’s mobile help site also provides a number of tips on improving the mobile experience to help you reach the goal of a one second page load.
Using these tools, you can determine your site’s load time. Which takes us to our next step — finding out how fast it should be. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
How Fast Does Your Site Need to Be?
The speed you should aim to achieve depends in part on what sort of site you have and what page you’re loading. Take, for instance, an ecommerce site. Generally for ecommerce, the page users land on first need to load much faster than the final pages of the buying process. That’s because visitors willingness to stay on a site increases along with their investment in that site.
Simply, the longer someone is on your site (say, completing a purchase), the more willing they are to stay, and less likely to be affected by load speed. The best way to determine how fast your page should be is to look generally at what other sites are doing. After all, it is a user’s experience across the internet as a whole that sets their expectations for what is fast and slow. Moz pulled together some data on this and this is what they found:
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]For your highly trafficked pages, any landing pages, and any internal pages that attract an unusual amount of inbound traffic, we’d recommend aiming to be in the top 10% of pages on the internet, with a load time of about 1 second. This correlates with a finding that half of all web users expect a site to load in 2 seconds or less. Of course, these guidelines should not be taken as law because a number of other factors play into the importance of load times. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
If you have qualified traffic landing on your site, for example, an internal page is ranking well for a recurring long tail keyword search, load times are less important because users are pre-qualified – they’ve specifically sought out your page. They’ll likely wait an extra second or more for it to load. On the other hand, site speed is absolutely critical for traffic where the user is poised to click away. This would include highly unqualified traffic, like traffic from PPC ads (especially if you’re bidding on keywords). Which brings us to the question of: what’s it going to cost you?
As we have seen, that depends on a number of factors. But there is a pretty clear relationship between load time and bounce. Google recently published a report showing the likelihood of abandonment the longer someone has to wait:
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”] [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]This makes perfect sense – the more time users spend waiting, the more likely they are to leave. This is also visualized in the following graph from KISS Metrics: [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
This is especially true on mobile networks, where load times are longer due to lower quality network connection. It’s hard to put a dollar value on this relationship, but Amazon tried back in 2007. With A/B testing, they found that every 100 millisecond delay resulted in losing 1% of sales. Another study in 2013 found that splitting load times in half from 15 to 7 seconds, and then again from 7 to 4, and so on, improved conversions, but had diminishing returns.
And finally, yet another survey from Gomez.com and Akamai.com found that a 1 second delay in load time would lead to a 7% drop in productivity. Obviously, the dollar value of these statistics is going to be different for everyone, but if you think about other techniques to optimize websites where a gain of even half a percent is a huge success, it starts to put the importance of speed into perspective.
Hotlinking is when you display an image on your website by linking to the same image that’s on another site. It’s a technique that lets you have big, beautiful images on your site, but avoids storing them on your server space. The thing is, whenever a web browser wants to load your web page, it has to go to an external source to get the image. That means more DNS lookups, which is slow. It also means you’re consuming bandwidth from someone else’s site, and the owner of the image can swap it out for something else at their own discretion.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]And it happens all the time. It would be pretty embarrassing to have something like this show up on your homepage: Hosting your own images is an easy way to cut out external links. Other sources of multiple DNS look ups include:
Social share buttons
Embedded YouTube videos or Twitter feeds
Google Web Fonts
Less look ups mean a faster site, so stop hotlinking! [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Google Developers very kindly has a whole section full of ideas for how you can speed up your website. One was is to install PageSpeed modules. PageSpeed modules are a series of modules that you can install for either Apache or Nginx that do a huge number of tiny tweaks to make each page on your site run faster. Each PageSpeed tweak is run as a filter, and you can turn these on and off as you see fit.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]PageSpeed filters help your site by:
Optimizing caching (e.g. outline CSS and JavaScript)
Minimizing round trips (e.g. CSS/JavaScript combining and flattening)
Prioritizing visual content (e.g. load above the fold stuff first)
Optimizing browser rendering (e.g. convert JPEG to progressive image loading)
PageSpeed modules provide a lot of technical speed boosts to your site in a really easy-to-implement way. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
3. Reduce HTTP requests
80% of a web page’s load time is spent on HTTP requests. HTTP requests include web pages, pictures, and files – basically anything that’s stored on the server. Therefore, one of the best ways to reduce your load time is to cut out some HTTP requests. There are dozens of ways to do this, so we thought we’d cover some of the easiest.
A CDN is a collection of servers spread all over the world. They speed your site in two ways.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]First, a CDN brings files closer to your user. For example, if your user is in Singapore and your servers are in Michigan, there’s going to be a big delay. But if you use a CDN, then it’s going to be like having a server in Singapore. Much faster. Second, CDNs shrink file sizes, so they load quicker. There are lots to join, but some of the most popular include CloudFlare, MaxCDN, Akamai (if you’re an enterprise company). [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
HTTP requests generally work like this. The web browser requests some information, and then the server sends it. That’s one HTTP request. But what if you want 10 things? Normally the web browser would request individually 10 things as 10 unique HTTP requests. It’d be like making a list for the grocery store and going taking 10 individual trips, one for each item. Very inefficient. A keep-alive header lets you keep the connection between the server and the web browser open, so you can send files over all at once, speeding things along.
Browser caching is when you save static components to a browser for future use by marking how often they need to be updated. Imagine, for example, a company blog page. You can’t cache the content, since you change the words every day or week or whatever.
However, let’s say that you have a logo on the same page. You can cache the logo, since you only update it every couple of years. So you mark the logo, telling the browser that it only needs to check for updates maybe once a year. That way, when a user is loading your blog page, their browser already has the logo read to go, and can concentrate on loading other stuff like words and images.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]There are caching tools out there to help you, but a lot of it is going to come down to you maintaining your site manually. The good thing is that you’ll find a lot of stuff doesn’t change that often, so once you mark it, you can pretty much leave it. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”] [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
5. Optimize your images
Humans are visual animals. So it’s no wonder that pictures have become a huge part of designing a website. Sadly, we often forget that the mobile networks have to download our big, beautiful hero images, which can spell disaster for load times. Fortunately, there are many ways you can streamline your pictures. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Size your images: when you upload an image (say, for a blog) the image is going to load to the largest possible size, and then resize to whatever it’s supposed to be. So if you upload a 1024×768 picture for an image that’s going to be resized to 300×200, it’s going to load all 1024×768 pixels of information before it resizes it. Upload the image you need.
Compress your images: most of your users won’t be able to tell the difference between a 100% image and a 70% image. But they will be able to tell the difference in load time. You can use the free tool compressor.io to easily compress your images without losing quality.
Progressive rendering: we’rebig fans. Give your users something to look at while they wait.
We know, we know – users shouldn’t have to click more than three times (allegedly). But if you bring everything as close as possible to the user, you’re probably looking at fewer, larger web pages. And larger pages are slower. You want to think carefully about the trade-off of one more click and smaller pages. Something else to think about is the user experience of having giant, scrolling web pages that go on and on.
Shorter pieces that are more to the point might drive your site a little better than one mammoth pile of information. If your pages are exceptionally long, we suggest you revisit your information architecture and see where you can group content together. Remember: the ideal page size is about 30KB.
Animations (including GIFs) can be used to explain something in a way pictures and words can’t, and background videos are fantastic for telling a story and engaging your users. We think both are great. But they’re expensive in terms of load time.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Use them sparingly to save your site from getting bogged down. Also, make sure they have a natural stopping point. For your background video, have it stop so it’s just an image after 1-2 loops. Better yet, you can have your video play on desktop but appear as a still image on mobile. For your GIFs and animations, a few loops should be plenty to get your point across. These are big ticket items for load time, so spend carefully. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
8. Minimize your font selection
Every time you use a custom font – or even one of Google’s – it’s going to increase your load time. System fonts are fastest, but obviously these aren’t right for everyone. If you do opt for a custom font or a web font, try and reduce the variety of fonts and weights that you use.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Also, pick one library and stick with it. For example, if you do decide to go for Google Fonts, then stick with that. Sure, it’s going to increase your load time vs a system font, since the web browser has to complete more DNS look-ups. But for each new font you add from Google Fonts, the speed difference is negligible. However, if you decide to combine fonts from two sources – for example, Google and Typekit –then that’s now more DNS look-ups the web browser has to make. The result is a slower load time. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default” custom_padding=”0px|||||”]
9. Simplify, simplify, simplify
Don’t get caught in the ‘look at all the cool stuff I can do’ trap. No one cares that your layout is the most creative ground-breaking use of CSS ever. Does it help the user? If not, then cut it. You need to be ruthless when you’re evaluating your website. Every animation, embedded video, social share, picture, and advertisement need to be critically examined for how it helps the user.
Look at Quick Sprout’s blog for a fantastic example. It’s simple. It’s basic. There are some images, there are some links, and there are some screenshots. But every single element is obviously there to help the user. Their austerity gets results– the Quick Sprout blog loads crazy-fast.
Plugins are so easy to implement that we tend to forget that they’re really quite heavy. Technically, it’s because the plugins have to make multiple calls to various servers, and that takes a while. It’s like if you had to go to the supermarket for 10 things, but could only take one thing at a time. So while they’re good to have, think carefully about each and every one.
Most personalization – featuring products that someone’s looked at before, recommended products, a customized home page etc. – requires a database lookup, which is going to take some time. It’s a small change, but again, over time these changes add up, so think carefully before you add that detail to your page.
Before you start battering down the doors, we are big fans of responsive design. It’s a great way to get a killer mobile experience while maintaining only one body of content. However, there is a flipside: namely, that there’s lots of extra code and technical weight that drags down load speed.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”] Responsive sites are almost always slower than their mobile counterparts, which again is going to be a problem for e-commerce companies. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
13. Fix your internal pages
As David Hsieh recently pointed out in a webinar, social media and other referrals mean that it’s not all about home page optimization anymore. Increasingly, users are bypassing homepages and ending up deep in a site, landing on blog pages or product pages. So optimization needs to extend all the way through the site, rather than be a front-loaded all-out effort on your home page or landing page
Ultimately, there’s no absolute figure for how fast you should be. Google says we should all be aiming for a one-second page load, which would put your site in the top 10% of sites on the web. B But speed can also be seen as relative. That is, it doesn’t matter how fast you are so long as you’re fast enough for your user. For example, a blog about different types of duck feather duvets, or something else equally niche, might tolerate a slower load time due to more qualified users seeking them out. Likewise, a site relying heavily on keyword-driven PPC instead of long tail SEO would likely need a faster load time for its less qualified users. What we do know is that over half of all users require a site to load in two seconds or fewer or they’ll leave, and both Walmart and Amazon have reported that faster load times have had a direct impact on their conversion rates. [/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_post_slider posts_number=”5″ include_categories=”2″ bg_overlay_color=”#0C71C3″ _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_post_slider][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_social_media_follow _builder_version=”4.9.10″ _module_preset=”default” text_orientation=”center”][et_pb_social_media_follow_network social_network=”facebook” url=”https://www.facebook.com/Gotmenownrp” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#3b5998″ follow_button=”off” url_new_window=”on”]facebook[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”twitter” url=”https://twitter.com/Gotmenow3″ _builder_version=”4.9.10″ _module_preset=”default” background_color=”#00aced” follow_button=”off” url_new_window=”on”]twitter[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”linkedin” url=”https://www.linkedin.com/in/gotmenow-soft-solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#007bb6″ follow_button=”off” url_new_window=”on”]linkedin[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”instagram” url=”https://www.instagram.com/gotmenow_soft_solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#ea2c59″ follow_button=”off” url_new_window=”on”]instagram[/et_pb_social_media_follow_network][/et_pb_social_media_follow][/et_pb_column][/et_pb_row][/et_pb_section]
Using WebP image format can reduce the image file size to more than 50% comparing with other image file type. For websites that using many images,using WebP image format will certainly boost the websites speed performance.
I also do some experiment to convert JPG and PNG images to WebP format. This JPG and PNG images I took by saving images fromMedia Player Classic(K-lite bundle), I don’t know anything about image compression or image format. To convert images to WebP, I am usingffmpegcommand line for Windows, and the result is:
PNG and JPG to WebP conversion reduce more than 60% in file size
Another experiment, I’ve done with this website NetworkReverse.com by changing all the posts images to WebP format. Fortunately, all images from this website posts are hosted in Google (bp.blogspot, ggpht,lh?.googleusercontent) and can be converted to WebP image format just by modifying the image url address. The result?
In this experiment I am usingGoogle PageSpeed Insight both Mobile and Desktopand the famousGTmetrixto test the website performance before and after conversion. The most significant thing I really impressed is the boost improvement in loading time (GTmetrix), it is almost a half from before conversion to WebP. Another thing is the Total page size, it is decrease more than 300KB, 25% smaller than before.
Unfortunately for now, WebP image format is not supported by all browsers yet. But most modern and widely used browsers already support WebP format. I’ve read some articles explaining about using a fallback image for browsers that doesn’t support WebP format. That will be my next experiment . Check thisBlogspot Image to WebP Lazy Loading Converter.
Anyway, if you are using blogspot and have your images hosted on bp.blogspot.com, you can try the trick from this video below to convert your images to WebP format by modifying url address andimprove your blogspot website speed performance.
Are you experiencing high bounce rates, low conversion rates, and other undesirable website metrics? While there are a multitude of different reasons as to why your site isn’t performing, one of the most overlooked reasons is site and page load speed.
First, let’s get the terminology down.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Site speed is how long it takes for your webpage to load from website hosting servers to the web browser that’s requesting the page. Page speed is slightly different, as it’s how long it takes for a page on your site to load after a link directing to it is clicked.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]While load speed is increases bounce rates and creates a poor user experience, it also affects your appearance in search. Google’s John Mueller even says it’s one of the most important factors in search visibility for the upcoming year in SearchEngineJournal’s recent podcast interview.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]You can find these metrics on your Google Analytics dashboard, or using a site speed tool.
In Google Analytics, go to “Behavior” on the left menu and click “Site Speed.”
To see site speed: Choose the first option “Overview.” From this page, you can see the average page load time, average server connection time, and other metrics on a broad scale. You can break this view down by browser, country, and page. Keep in mind, this report just shows averages, but what’s cool about this is you can view different time periods. By doing that, you can infer what changes caused slowdowns in the site.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]To see page speed: Choose the second option under “Site Speed” on the left menu – ”Page Timings.”
In this view, you are able to see how each individual page loads. This report shows how the speed compares to your site’s average load speed, and you can even break it down by load time in seconds, bounce rate, page views, and more.
[/et_pb_text][et_pb_image src=”https://blog.gotmenow.com/wp-content/uploads/2021/09/Speed-up-your-PC.jpg” alt=”improve site speed” title_text=”improve site speed” align=”center” _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_image][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]To see an overall report on all of your site’s pages, Google Search Console recently updated their dashboard to include a Speed Report. This is currently an experimental tool on the dashboard, but it will showcase which specific pages have errors and are loading slow, moderate, or fast.
As for site speed tools, Google has PageSpeed Insights, which gives a very vivid diagnosis on how long it takes for the first contentful paint to load, the first meaningful paint, and other speed data. It provides screenshots from the initial load and also provides very actionable opportunities based on the insights from the test.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]WebPageTest is another tool for a quick overview of your site’s speed. This tool allows you to pick a device and a location to test from, and will provide a report that presents the site’s total load time, the load time for first contentful paint, speed index, and additional nichey data.
Now you’re probably wondering what a good speed to have is… however, every site is different. Obviously a simple single page site is going to load a lot quicker than a robust site full of animations, scrollytelling effects, and high quality retina visuals. It also depends on the server fetching the data, and other factors that you can’t actually see as a user. So if we’re talking about a good user experience, all excuses aside, anything longer than 3 seconds is too long – Google said so. And that’s still about 2.5 seconds too long, as Google also says users only want to wait about the length of a literal blink of the eye… 400 milliseconds. That’s asking a lot, though.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]So, how do you get to a load speed that’s under 3 seconds? As you probably understand by now, a lot of factors go into this number. For site load speed, there’s not really an easy fix. To do this properly, you’re going to want to have your developer look into a few things…
[/et_pb_text][et_pb_image src=”https://blog.gotmenow.com/wp-content/uploads/2021/09/how-to-fix-a-slow-website.jpg” alt=”improve site speed” title_text=”improve site speed” _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_image][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Remove old and unused code, themes, databases, apps and anything else that’s cluttering the backend of the site;
Optimize site wide assets, like your logo, items that appear in the footer, badges, etc.;
Reduce the amount of http/s requests, as the more files there are, the more requests are run and the longer the load takes;
Minify JavaScript, CSS, and HTML files, because like I said, the less code the better.
Page speed is a little more fun (well… fun for me). You’re going to have to do some digging to figure out what needs to be optimized. Start by going to that “Page Timings” report in Google Analytics. Ask yourself these questions:
What pages are the slowest? How slow?
What pages have the highest bounce rates? And the lowest bounce rates?
If bounce rates are high (at Electric Enijn, we like to see bounce rates under 40%), but the time spent on the page is also high – what’s keeping users on the page? Could that be slowing down the page?
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Gather all of these insights all in one place and start looking at the pages on your site. Sometimes the answer is obvious, like the page has a lot of images, videos, and different fonts. But maybe the page looks the same as others, and it’s still a lot slower. This is when you’ll have to look a bit further into what makes up the page. If there are old scripts, font families, or anything else being pulled onto the page but not actually being used, take them out. We recommend using Google Fonts, which are also optimized for page speed. The same goes for plug-ins, tracking pixels, and any type of widget, similar to what you would want to look for sitewide to improve site speed.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]As for images and videos on the page, try and shrink their size. One tool we often use for compressing PNGs and JPEGs is Tinypng. If they can’t be optimized any further, you might have to try lazy loading them in. This isn’t the best practice for SEO, but hey, site speed is SEO, too!
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]After optimizing your site to improve load speed, keep testing it and see if your metrics improve. If it doesn’t seem to be loading faster, it might be a deeper issue if your CMS or hosting platform. A lot of WordPress sites, for example, are weighed down by excess themes, scripts, and plug-ins, but the deeper site speed issue tends to be the hosting platform. While the promise of “unlimited” bandwidth, email accounts, and cloud space are appealing, what you should really be looking for from your site host is a high uptime, no less than 99%. Many self hosting CMS’ can offer unbeatable uptime, like Shopify promises 99.98%. We’re big fans of wpengine, which will monitor for bad plugins and ensure your website stays compliant.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]I recommend you check your website’s site speed by digging into your Google Analytics or using one of the speed tests to see how your website is performing. While 3 seconds is ideal, your site is probably hovering around 15 seconds – and this wait time increases a user’s probability of bouncing by over 123%. While it’s important to get this metric down, it’s more important that you do it properly by keeping both your site’s structure and user experience in mind.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_post_slider posts_number=”8″ include_categories=”2″ bg_overlay_color=”#0C71C3″ arrows_custom_color=”#0C71C3″ _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_post_slider][/et_pb_column][/et_pb_row][et_pb_row _builder_version=”4.9.10″ _module_preset=”default”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_social_media_follow _builder_version=”4.9.10″ _module_preset=”default” text_orientation=”center”][et_pb_social_media_follow_network social_network=”facebook” url=”https://www.facebook.com/Gotmenownrp” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#3b5998″ follow_button=”off” url_new_window=”on”]facebook[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”twitter” url=”https://twitter.com/Gotmenow3″ _builder_version=”4.9.10″ _module_preset=”default” background_color=”#00aced” follow_button=”off” url_new_window=”on”]twitter[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”linkedin” url=”https://www.linkedin.com/in/gotmenow-soft-solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#007bb6″ follow_button=”off” url_new_window=”on”]linkedin[/et_pb_social_media_follow_network][et_pb_social_media_follow_network social_network=”instagram” url=”https://www.instagram.com/gotmenow_soft_solutions/” _builder_version=”4.9.10″ _module_preset=”default” background_color=”#ea2c59″ follow_button=”off” url_new_window=”on”]instagram[/et_pb_social_media_follow_network][/et_pb_social_media_follow][/et_pb_column][/et_pb_row][/et_pb_section]
Having a hotel website is essential for attracting guests and allowing them to book conveniently.
Without it your target audience won’t even know your business exists and your cost of acquisition will be high.
Although the overall aesthetic is important, it’s not all about how your website looks. Site speed can sometimes be overlooked when a business draws up plans for a new hotel website.
There is little point in spending thousands on design and SEO to attract guests if their first experience of your site is an irritating wait or an unresponsive page.
Browsers won’t wait 5-10 seconds for the page to load, instead they are likely to exit and visit your competitor’s hotel website.
Early in 2020, Google announced it was making changes to its algorithm so that page speed will be added as one of the ranking signals.
In 2021, Google will be doubling down with the introduction of Core Web Vitals (CWVs).
The new CWVs consist of a list of technical SEO metrics including three new ways to think about and measure page speed.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Google’s main priority is to provide your audience with the best content along with a great (fast) experience.
The benefits of a speedy site are numerous, including increased engagement, lower bounce rate, and ultimately increased revenue.
The higher the speed, the higher the conversion.
Let’s take a look at some of the main factors which affect site speed and how they can be optimised.
There are many factors that will dictate how quickly your server responds but some of the most critical are:
Hardware resources available to your application (include hosting infrastructure): This refers to everything from the server’s processor speed to its network connection. It’s important that your host gets this right.
Server site caching: Using a site cache will provide greatly increased performance. Instead of having to query your database or external web services for data every time a page is requested, the cache temporarily holds page data so that content can be quickly loaded again as required.
Database optimization: There are many ways of optimizing your database for fast reads. By doing so, you speed up the loading time for your site as a whole not just the page the browser currently displays. An experienced database administrator can go much deeper into the optimization process but there are often some quick wins which can deliver huge gains.
Your web browser is a software application which also has a cache. As this application searches, identifies and shows us the websites your browser cache will save information, data, and images.
You can leverage browser caching by configuring your server to attach an expiry date to each resource (image page, stylesheet, etc).
The next time the browser requires it, it will check the local cache to see if the resource is within date. If so, it uses the local copy and there is no need to pull data from the server.
Over time more content will be added to your site. This will inevitably include photos and images which may not have been sized correctly.
These large files can use enormous amounts of bandwidth and often lead to an undesirable lag in page load speed, especially on mobile devices.
Resizing and optimizing images appropriately can reduce the image file size, and therefore loading times, by as much as 95% without any observable loss in quality.
There are many easy-to-use tools available for download online that will compress, resize, and optimize your images.
When your web page begins to load it may display the header, then pause before loading the rest of the page.
This pause may be due to an issue called render blocking of the scripts. The site is having to load style and theme instructions before it can display the content.
As with any of the issues described in this article the key is to be aware of speed issues which on their own may not be a problem but when compounded can cause severe problems which will lead to higher bounce rates, less conversions and lower rankings from Google.
It is one of the reasons why working with a specialist agency such as Aró is so important. Every detail matters when there is a need for speed.
Is the Website Loading speed really that important?
You must remember the beginning of the Internet, the connection through modems and slow websites. Luckily, that time is behind us and the websites are getting faster and faster. Website loading speed is very important for the user experience. Therefore, the page loading speed has become an official ranking factor from a search engine perspective. The upper page load limit is up to 2 seconds, and the ideal one is about 0.5-1 seconds. In this post we’ll write some tips onhow to improve website loading speed.
Tips on How to Improve Website Loading Speed
There are a bunch of online services where you can check the speed of your site for free. Even Google offers free online servicePageSpeed Insights. All you need to do is to enter the site’s url which you want to analyze, and wait for a few seconds:
Full-resolution images can take a long time to load. Images that have not been compressed causes slow loading, especially on mobile devices. No image should be over 100kb and you should never upload images directly without optimization and resizing.
Luckily, there is no need for high level of development skills for this, and you can easily reduce the size of your images, without any quality degradation through a number of free tools and plugins, if you have WordPress website. Images can be edited and loosely compressed using Photoshop/Illustrator and with many other free online tools.
Also, there are many tools and plugins for WordPress users that will automatically compress your images as you are uploading it to the website, likeWP Smush.
2. Remove Render-blocking CSS and JavaScript files
CSS & JavaScript files are very important for your website, because they control how your site will look and function. Render-blocking CSS and JavaScript files prevent your page from fully loading until they are processed.
You should avoid and minimize the use of blocking JavaScript and CSS files. If you have a lot of small CSS files, try to put them into one CSS file if possible. To remove Render-blocking Js you can make JS Asynchronous or preform Defer Loading of JS.
A CDN can speed up your site by serving static files such as images, CSS, Javascript and other static files. A CDN will store your website’s static files (CSS, JavaScript, images, fonts, etc.) into a non-centralized file system around the world, and when user from another country visits your website, CDN will serve the files from the closest server to user’s location.
4. Enable the Website Compression
Website Compression can reduce the size of text-based files that the browser has to download and you’ll be surprised with results after enabling the compression.
The most popular compression tool for HTML, CSS and JavaScript text-based elements isGZIP. The configuration depends on your server. For Apache web server you’ll need to put some configuration rules into .htaccess file. For WordPress users there are always suitable plugin, checkWP Super Cache.
5. Cache Your Website
Server Rendering time can really slow your website, but when your site is cached properly it can reduce your website’s loading time. Caching makes websites extremely fast, which leads to better SEO scores. Browser caching allows pages to load quicker as users navigate through the website by telling the browser how long to keep files stored. There are two very popular plugins for WordPress users: W3 Total Cache & WP Super Cache.
6. Minify HTML, CSS and JavaScript
Minifying HTML, CSS and JavaScript involves removing redundant text from a file, such as unnecessary text, data, white spaces, comments, characters, etc. t is recommended to perform minification just before releasing into production, as developers wont be able to read/edit them easily.
Removing redundant formatting, code comments and unused code will enable very fast loading time. There are plenty of free tools you can use to minify your files manually or automatically:Minify for CSS & JavaScript minification,JSCompressfor JavaScript minificaton, etc. As always there is W3 Total Cache for WordPress users, but this part can be a little advanced for beginners.
Out of many performance metrics, one which matters the most is Time To First Byte (TTFB). If TTFB is worse, then it is guaranteed to be a poor performing website connection. TTFB depends upon many factors. One very critical factor is server connection which happens after DNS resolution. I will discuss how to optimize server connection speed in this article. We will look into how TLS 1.3 and HTTP/3 improves website performance. We will also look into other optimization possibilities like ECC certificates and OCSP stapling.
Insecure (HTTP) tends to be faster than secure (HTTPS) connections because of the encryption overhead in HTTPS. The difference becomes insignificant as more data processing happens.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]If security is not a concern and performance is supercritical then using HTTP can give some performance gain. I will not recommend doing this because of the following reasons.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Browsers are getting more and more restrictive towards HTTP. Firefox released HTTPS-Only Mode in version 83.
Chrome planning to assign an insecure badge to sites not using HTTPS. This will be very bad for branding.
The performance gain will be very insignificant in front of the security issues and losing the user’s trust.
Using a mix of HTTP and HTTPS can open security loopholes for the encrypted requests as well.
Making a secure connection to the server is a tedious task. Client and Server both go through numerous steps before start sharing data with each other.
Transport Layer Security(TLS) is an encryption protocol used to encrypt and decrypt data over HTTP protocol. Both HTTP and TLS have come a long way to provide more secure and performant server connections.
TLS 1.2 which was released in 2008 has served the web for a very long time. It has few security and performance issues which were taken care of in the new shiny TLS 1.3.
TLS 1.3 is well supported in all major browsers and as per caniuse.com data, more than 90% of the users have TLS 1.3 support
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]TLS 1.3 comes with lots of improvements from its previous versions. It dropped support for many weaker encryption algorithms. Tries to achieve perfect forward secrecy, which is a process of changing key for each session so that a compromised key will not affect other sessions.
For performance, TLS 1.3 made two major changes over TLS 1.2
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Dropped a complete one round trip to establish a server connection.
0-RTT reduces one more round trip for repeat users by using the previously captured information during the initial connection. 0-RTT is prone to replay attacks which can be solved with proper precautions.
Because of the security issues with 0-RTT, It is not well supported in major browsers and servers.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]TLS 1.3 is supported in all major browsers and servers. It also has out of the box support in a few CDN’s like Akamai and Cloudflare.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]TLS 1.3 is supported in all major browsers and servers. It also has out of the box support in a few CDN’s like Akamai and Cloudflare.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
HTTP/2 was a major upgrade over its previous version. It has many optimization features that can significantly boost web performance.
The major focus on HTTP/2 design was to make full use of available network bandwidth. It multiplexes requests on a single connection. Browser’s limit around the number of parallel requests on a domain is not valid on HTTP/2. There is no need to create multiple domains to bypass browser restrictions on parallel requests on a single domain.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]HTTP/2 released server push where the server can send multiple responses for a single request. It was a great idea as in most cases webpages are aware of what will be the next request. Server push has the limitation that it is not aware of browser cache and can send data even when It can be served from the browser cache. There are workarounds but they are not very reliable and tough to put in place.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]Server push was not very well adopted because of its limitations. In November 2020 browsers and servers planned to remove support for server push.
By enabling HTTP/2 most of its features are out of the box available without doing anything.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
In HTTP/2 messages are broken into frames and sent over the network stream. This makes multiplexing of requests possible on a single domain. This means only one connection is required for a domain to transfer all data.
The above statement is not fully correct. There are edge cases where multiple connections are required on the same domain. HTTP/2 session reuse does not happen across credentialed and uncredentialed requests. Fonts will always create a new connection as they are downloaded as an uncredentialed request.
Every request has some metadata associated with it. Headers are one such metadata. In previous versions, headers are passed as plain text which sometimes occupies a few KBs of the request payload. In HTTP/2 headers are compressed using the HPACK algorithm.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
HTTP/1.x has the limitation that responses can be received only one after another. This causes responses to queue and waits for their turn before usage.
In HTTP/2 this got fixed because of the multiplexing approach. The response is ready for consumption as soon as it completes.
HTTP/2 fixes head-of-line blocking when receiving the response but It still has another kind of head-of-line blocking which is fixed in HTTP/3 protocol.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]
Prepare for the new hotness HTTP/3
All HTTP protocols before HTTP/3 uses TCP for communication as it was more reliable. TCP ensures to send an acknowledgment for every packet and guarantees packet order. This makes request and response very reliable at the cost of some performance limitations.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]HTTP/2 faces head-of-line blocking on the unreliable network when a packet fails to deliver. This is because of how TCP works. If a packet fails than all subsequent packets even from other request needs to wait as they are part of a single multiplex connection. This becomes serious as HTTP/2 multiplex many requests and all get blocked because of a single packet failure.
let we have 3 responses A, B, and C each consists of 5 data packets 1 to 5.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]In HTTP/2, if the B1 packet fails then all A, B, and C responses will fail to deliver.
In HTTP/3, if the B1 packet fails only the B response will block, and the rest A and C will deliver as expected.
HTTP/3 solves this HTTP/2 issue of head-of-line blocking by using UDP instead of TCP.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]On a reliable network, HTTP/3 might not have any benefit over HTTP/2 but on an unreliable network (like a mobile network) HTTP/3 will shine.
HTTP/3 does not have very good browser support for now. Chrome support for HTTP/3 will land in version 85. Server-side support is also improving. Nginx and Node have already released HTTP/3.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default” hover_enabled=”0″ sticky_enabled=”0″]
Elliptical Curve Cryptography(ECC) Certificates
Certificate Authority(CA) issues domain certificates to individuals and organizations after proper verification. The verification steps can differ from one CA to another. Free CA like letsencrypt have very basic verification steps while paid services like DigiCert have more robust verification steps.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]CA provides different kinds of certificates based on the verification steps and support for different encryption algorithms. For some certificates browsers mentions the organization name with the secure badge, this adds more trust to the customers.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]One very secure and fast algorithm is elliptical curve cryptography (ECC). ECC certificates provide strong security and fast encryption and decryption. The speed of encryption/decryption depends upon the size of the key and mathematical computation around it. ECC certificates have both of them in the limit. When the RSA key size starts from 1024 bit, the ECC key size starts from 160 bit.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]For your next certificate prefer to buy an ECC certificate over others.
Do not forget to check browser support for the ECC certificate. It is not very well supported in legacy browsers like IE11
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Your content goes here. Edit or remove this text inline or in the module Content settings. You can also style every aspect of this content in the module Design settings and even apply custom CSS to this text in the module Advanced settings.
Online Certificate Status Protocol (OCSP) stapling
Browsers download a certificate from the server and to verify the authenticity of the certificate it recursively downloads certificates used to sign the current one until finds the root certificate.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]To avoid this entire process server can query the OCSP responder. OCSP responder is the Certificate Authority server which provides a digital signature to verify the certificate. The server can cache the query response and now the browser will have to only verify the CA signature.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]OCSP stapling has good server and browser support but the most popular AWS ELB and ALB lack behind in OCSP stapling support.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]OCSP stapling has good server and browser support but the most popular AWS ELB and ALB lack behind in OCSP stapling support.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]OCSP stapling has good server and browser support but the most popular AWS ELB and ALB lack behind in OCSP stapling support.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]OCSP stapling has good server and browser support but the most popular AWS ELB and ALB lack behind in OCSP stapling support.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default” custom_padding=”26px|||||”]
Conclusion
Prefer to use TLS 1.3 for strong and fast encryption and decryption of data over the network.
Prepare for HTTP/3 It will be around the corner in the next few months.
Prefer ECC certificates they are fast and more secure than RSA or SHA based algorithms.
OCSP stapling is a very simple and effective web performance optimization.
[et_pb_section fb_built=”1″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_row _builder_version=”4.9.10″ _module_preset=”default” custom_padding=”||61px|||”][et_pb_column type=”4_4″ _builder_version=”4.9.10″ _module_preset=”default”][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]The road to high website ranking is paved with all manner of things that can both accelerate performance and act as speed bumps along the way. Of the myriad factors that can bolster page ranking, website page speed is something of an SEO hot potato right now – especially with Google’s recent announcement that website page speed will also influence page ranking in mobile searches earlier this year.
But how exactly does website page speed affect search rankings and why does it matter? And, if a website is particularly sluggish, what can be done to improve its pace and enhance its potential to rank highly in page searches? With Banc’s know-how of technical SEO, we’ll answer this triad of enquiries over the course of this very article.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
How does page speed affect search rankings?
First off, it’s worth noting that Google may measure Time to First Byte (TFFB) when it considers page speed, i.e. the duration of time from the user’s browser making a HTTP request to the first byte of information that’s returned by the server. It’s a matter of milliseconds usually, but Google feels it necessary to begin measuring website page speed at this point. In fact, the tech giant conducted a study that showed slowing down the search results page by 100 to 400 milliseconds – a trifling amount by anyone’s watch – had a noticeable impact on the number of searches per user. According to Google, your website’s TTFB should be 200 milliseconds or less.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]From a UX perspective, a website with a higher TTFB can be an annoyance. The slower the page and longer its load time, the more likely it is that a page’s bounce rate (the percentage of visitors that navigate away from the site after viewing only one page) will increase. The lower average time on page and longer TTFB are taken into consideration by Google, which can negatively affect your website’s SERP rank as a result. A good user experience often translates to higher conversions and thus, higher page rankings – it’s that simple. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]And in the world of UX, patience is not a virtue; users do not like to be kept waiting when it comes to page speed. Almost half of users want pages to load within a maximum of two seconds, and even a 1-second delay on load speed can reduce conversions by around 7%. Does a particular page on your site load for longer than 4 seconds? Studies have shown that 75% users won’t return to a page if they’re kept waiting longer than this. The gulf between a page taking two seconds to load and one loading at twice that time may as well be a Grand Canyon-esque chasm. [/et_pb_text][et_pb_image src=”https://blog.gotmenow.com/wp-content/uploads/2021/09/page-loading-speep-723275503-ss-1920-1-800×450-1.jpg” alt=”website page speed” title_text=”website page speed” _builder_version=”4.9.10″ _module_preset=”default”][/et_pb_image][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Why does this matter?
With Google looking to make the web more mobile-friendly, mobile-first indexing is just around the corner. “What’s mobile-first indexing?” we hear you ask. It’s fairly simple. It means that the mobile version of your website becomes the starting point for what Google includes in their index, using it as the baseline for how they determine rankings on both mobiles and desktop. As a result, the importance of website page speed increases accordingly. If your site doesn’t have a mobile equivalent, the desktop site can still be included.
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]However, the lack of a mobile experience could negatively affect rankings on desktop, whereas a good mobile experience serves to boosts ranking even for searchers on a desktop. Think of it like this: the mobile version acts as the primary version of your website. [/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
How to improve your website page speed
Tools such as Lighthouse, Pagespeed Insights, GTMetrix and WebPageTest allow us to glean information on how pages are loaded, providing us with valuable insights on how to reduce page speed in the process. Using insights from the tools above, you can get an idea of what needs to boost the speed of your web pages.
Here are some of the most common ways to reduce load times and improve page speeds
[/et_pb_text][et_pb_text _builder_version=”4.9.10″ _module_preset=”default”]
Leverage browser caching – Browsers such as Chrome, Firefox and Edge cache large amounts of information like Javascript files, stylesheets and images, so when a user revisits a site, it doesn’t have to reload the entire page. By setting an expiry date within the HTTP header, it allows us to control how long we want information to be cached.
Improve server response time – Server response times tend to be affected by the amount of traffic a site receives, the resources each page uses, the software the server uses and the hosting solutions being used. To improve this, further research into how the server is performing may be necessary, clearing up any issues with slow routing or slow databases in order to clarify if these affect website page speed.
Enable compression – CSS and Javascript files can sometimes cause a large load time, and more so for big inline individual files being used on a site. By compressing these files into one chunk, the overall size of these files gets pared down and the load time decreases as a result.
Use a content distribution network (CDN) – CDNs, such as Cloudflare, are networks of servers that are used to distribute the load of delivering content. Essentially, copies of a site are stored at a range of geographically diverse data centres so that users have faster and more reliable access to a given site
Optimise images – The size and file format of images used on a site can adversely slow it down. Sometimes this is because of extra data embedded in the comments or a lack of compression. Newer, next-gen image types, like WebP, JPEG 2000 and JPEG XR, can reduce the size of files in a big way.
Miscellaneous factors – A cluttered page will only serve to clog up your site’s page loads, so be mindful of any superfluous features which might be responsible. External embedded media, like videos, might look great and serve a purpose but can increase load times. Likewise, plugins and apps, when used on unoptimized browsers, can drastically slow down your page speed. Consider the use of widgets; are they helpful or just window dressing that may be negatively impacting your page?
