The first step to improving your SEO is understanding how you're currently performing. Below, we have compiled a list of some of the most important ranking factors, and have given you a score for each one. If you want to learn more about how you can improve your rankings then sign up for the Hike platform where you'll learn how to increase traffic on your website by managing your own SEO efforts.
There are a lot of areas where you can improve the SEO of your website. Don't be downhearted; this means there's lot of opportunity available for better rankings!
Your website does not rank very well in Google. Below shows you how many keywords your website appears for in Google vs your top competitor. As you can see you there are not enough keywords on page 1.
You want to aim for the top 5 positions for every phrase, as this is how you will drive the most traffic. Want to improve your rankings? Make a start on the actions detailed further down the report.
100%
lower than your top competitor
Here are up to 25 of the top keywords that both your website and your competitor's website rank for. Are your key products and services being highlighted?
Below are up to ten SEO actions we recommend you make to your website now to improve the onsite SEO. We have also found more actions for your website (that covers all your website pages) that will help your website rank higher in the Google search results.
There are no actions for your website
Below is your page speed score for your website's homepage on a mobile. The higher the number, the better the performance. Currently, there is a lot of improvement required for your website so it loads faster. This will not only impact your SEO performance but also your customer experience.
Below the scores you will find a list of actions you can take to improve your website's speed. These are bespoke recommendations direct from Google for your website.
Serve static assets with an efficient cache policy
HTTP caching can speed up your page load time on repeat visits.
When a browser requests a resource, the server providing the resource can tell the browser how long it should temporarily store or cache the resource. For any subsequent request for that resource, the browser uses its local copy rather than getting it from the network.
The below table lists all static resources that aren't cached;
| url | cacheHitProbability | cacheLifetimeMs | totalBytes | wastedBytes |
|---|---|---|---|---|
| 0 | 0 | 55317 | 55317 | |
| 0 | 0 | 31673 | 31673 | |
| 0 | 0 | 31212 | 31212 | |
| 0 | 0 | 1277 | 1277 | |
| 0.14 | 1800000 | 20936 | 18057.3 | |
| 0.2 | 3600000 | 1949 | 1559.2 | |
| 0.25 | 7200000 | 20664 | 15498 | |
| 0.92 | 7776000000 | 230686 | 17720.29 | |
| 0.92 | 7776000000 | 124118 | 9534.2 | |
| 0.92 | 7776000000 | 73098 | 5615.07 | |
| 0.92 | 7776000000 | 53975 | 4146.12 | |
| 0.92 | 7776000000 | 49505 | 3802.76 | |
| 0.92 | 7776000000 | 43940 | 3375.28 | |
| 0.92 | 7776000000 | 43793 | 3363.99 | |
| 0.92 | 7776000000 | 39308 | 3019.47 | |
| 0.92 | 7776000000 | 37137 | 2852.7 | |
| 0.92 | 7776000000 | 34188 | 2626.17 | |
| 0.92 | 7776000000 | 26926 | 2068.34 | |
| 0.92 | 7776000000 | 26158 | 2009.34 | |
| 0.92 | 7776000000 | 25770 | 1979.54 | |
| 0.92 | 7776000000 | 23030 | 1769.06 | |
| 0.92 | 7776000000 | 22274 | 1710.99 | |
| 0.92 | 7776000000 | 21169 | 1626.11 | |
| 0.92 | 7776000000 | 20685 | 1588.93 | |
| 0.92 | 7776000000 | 18223 | 1399.81 | |
| 0.92 | 7776000000 | 17522 | 1345.96 | |
| 0.92 | 7776000000 | 16654 | 1279.29 | |
| 0.92 | 7776000000 | 16568 | 1272.68 | |
| 0.92 | 7776000000 | 16391 | 1259.09 | |
| 0.92 | 7776000000 | 12549 | 963.96 | |
| 0.92 | 7776000000 | 12056 | 926.09 | |
| 0.92 | 7776000000 | 11211 | 861.18 | |
| 0.92 | 7776000000 | 10847 | 833.22 | |
| 0.92 | 7776000000 | 10493 | 806.03 | |
| 0.92 | 7776000000 | 10398 | 798.73 | |
| 0.92 | 7776000000 | 10019 | 769.62 | |
| 0.92 | 7776000000 | 8368 | 642.79 | |
| 0.92 | 7776000000 | 8220 | 631.42 | |
| 0.92 | 7776000000 | 7626 | 585.8 | |
| 0.92 | 7776000000 | 7249 | 556.84 | |
| 0.92 | 7776000000 | 5793 | 444.99 | |
| 0.92 | 7776000000 | 5776 | 443.69 | |
| 0.92 | 7776000000 | 5068 | 389.3 | |
| 0.92 | 7776000000 | 4279 | 328.69 | |
| 0.92 | 7776000000 | 4234 | 325.24 | |
| 0.92 | 7776000000 | 3775 | 289.98 | |
| 0.92 | 7776000000 | 3508 | 269.47 | |
| 0.92 | 7776000000 | 3152 | 242.12 | |
| 0.92 | 7776000000 | 3107 | 238.67 | |
| 0.92 | 7776000000 | 2966 | 227.84 | |
| 0.92 | 7776000000 | 2890 | 222 | |
| 0.92 | 7776000000 | 2730 | 209.71 | |
| 0.92 | 7776000000 | 2635 | 202.41 | |
| 0.92 | 7776000000 | 2607 | 200.26 | |
| 0.92 | 7776000000 | 2548 | 195.73 | |
| 0.92 | 7776000000 | 2474 | 190.04 | |
| 0.92 | 7776000000 | 2445 | 187.81 | |
| 0.92 | 7776000000 | 2333 | 179.21 | |
| 0.92 | 7776000000 | 2036 | 156.4 | |
| 0.92 | 7776000000 | 1987 | 152.63 | |
| 0.92 | 7776000000 | 1928 | 148.1 | |
| 0.92 | 7776000000 | 1807 | 138.81 | |
| 0.92 | 7776000000 | 1759 | 135.12 | |
| 0.92 | 7776000000 | 1747 | 134.2 | |
| 0.92 | 7776000000 | 1591 | 122.21 | |
| 0.92 | 7776000000 | 1580 | 121.37 | |
| 0.92 | 7776000000 | 1569 | 120.52 | |
| 0.92 | 7776000000 | 1553 | 119.29 | |
| 0.92 | 7776000000 | 1147 | 88.11 |
Reduce JavaScript execution time
When your JavaScript takes a long time to execute, it slows down your page performance in several ways:
Network cost
More bytes equals longer download times.
Parse and compile cost
JavaScript gets parsed and compiled on the main thread. When the main thread is busy, the page can't respond to user input.
Execution cost
JavaScript is also executed on the main thread. If your page runs a lot of code before it's really needed, that also delays your Time To Interactive, which is one of the key metrics related to how users perceive your page speed.
Memory cost
If your JavaScript holds on to a lot of references, it can potentially consume a lot of memory. Pages appear janky or slow when they consume a lot of memory. Memory leaks can cause your page to freeze up completely.
An overview of the files found are below;
| url | scriptParseCompile | scripting | total |
|---|---|---|---|
| 38.09 | 699.55 | 1312.29 | |
| 62.37 | 531.18 | 739.82 | |
| 0 | 51.98 | 737.8 | |
| 29.27 | 438.55 | 600.81 | |
| 16.35 | 369.08 | 506.96 | |
| 6.22 | 449.51 | 477.88 | |
| 1.86 | 114.59 | 418.41 | |
| 16.87 | 275.77 | 310.5 | |
| 65.14 | 171.68 | 252.98 | |
| 9.38 | 17.73 | 208.32 | |
| 1.05 | 198.34 | 206.07 | |
| 13.46 | 113.94 | 169.53 | |
| 0.44 | 115.83 | 157.23 | |
| 12.1 | 124.38 | 137.72 | |
| 12.42 | 97.76 | 118.4 | |
| 53.59 | 63.39 | 118.12 | |
| 7.54 | 103.18 | 114.68 | |
| 11.08 | 57.4 | 69.36 | |
| 3.43 | 48.76 | 58.95 | |
| 0.64 | 49.12 | 57.92 | |
| 8.24 | 41.87 | 53 | |
| 5.27 | 38.84 | 52.32 | |
| 13.1 | 35.62 | 50.09 |
Reduce unused CSS
Below we have listed all stylesheets with unused CSS with a potential savings of 2 KBs or more. Remove the unused CSS to reduce unnecessary bytes consumed by network activity:
| url | totalBytes | wastedBytes | wastedPercent |
|---|---|---|---|
| 22274 | 22274 | 100 | |
| 16654 | 16654 | 100 |
Your backlink score isn't very good - you need to build some backlinks. Below shows you how many backlinks your website has vs your top competitor.
A backlink is a link from another website to yours, and it really helps your SEO. At the moment, your backlink score is very low and it is because you have a small number of backlinks from valuable websites, so you want to improve this as soon as possible.
100%
lower than your top competitor
99%
lower than your top competitor
---
Here are up to 10 of the top backlinks you and your competitor have. Can you see any opportunities from your competitor?
13th Jan 2023
9th Jan 2023
7th Jan 2023
5th Jan 2023
10th Jan 2023
4th May 2022
20th Dec 2021
17th Jul 2022
12th Dec 2022
14th May 2021
17th Apr 2022
9th Jan 2023
18th Apr 2022
2nd Dec 2020
5th Dec 2020