from the worst...
Share this report by email
Feel free to share this report with your collaborators, by copying the URL from the address bar,
or by clicking below:
Share the report
Tips and best practices:
Things to improve
Optimize your images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 149.4KiB (40% reduction).
Resources from "com"
- Losslessly compressing seotools.com.np/th[...].png could save 4.5KiB (50% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 4.1KiB (48% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.9KiB (50% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.9KiB (70% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.8KiB (59% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.8KiB (37% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.8KiB (48% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.5KiB (35% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.5KiB (32% reduction).
- Losslessly compressing seotools.com.np/th[...].png could save 3.3KiB (31% reduction).
- and 38 others
Resources hosted by a third-party
It appears these files are hosted by a third-party, so they may not be within your control. However, you should consider any alternative to these resources to improve your page performance.
- Losslessly compressing res.cloudinary.com[...].jpg could save 1.1KiB (7% reduction).
57 of your requests don't define a cache policy
Expires header is essential for an efficient caching policy. It will significantly impact on the loading time for returning visitor.
The Expires header explained
You can set an expiration date for each resource: as long as the date is not exceeded, the browser stores and uses the resource in cache.
The expiry date of resources is set using the
Expires HTTP header:
Expires: Thu, 25 Dec 2014 20:00:00 GMT
You can set a far expiry date for static resources (1 year maximum), and a closer date for resources that change more frequently (at least 48 hours).
When you deploy a new version of your website, remember to rename static resources that have been modified. If you do not change their names, your users will keep resources corresponding to the old versions stored in their caches, and they may find themselves on an unstable version of your page. For example:
See the Yahoo! guidelines on this subject.
This page contains 57 resources without expiry date:
- and 50 others
The PNG format is not the most suitable for 6 of your images
The choice of the right format for an image allows to reduce its weight.
The PNG format
The PNG image format is intended to the images requiring the transparency, or else to the small images having little details and colours.
Prefer the JPEG format...
The main problem of PNG format is to not support quality loss. Indeed, a format such as JPEG offers to "downgrade" the quality of the image without being perceived by the user. Doing so, you can reduce the quality of the image of about 25% whithout the user realizes it.
An image with an consequent weight will be therefore better compressed by using the JPEG format.
...or the PNG-8 format
In the case where your image necessarly requires using the transparency mecanism, not borne by the JPEG format, you should convert your "standard" PNG image, into PNG-8. This format, based upon a 256 color palette maximum allows to decrease the weight of the image whithout significantly affecting its overall quality. Tools such as pngquant or else tinypng will suport you in this procedure.
At last, if the quality given by the PNG-8 format is not appropriate for your image, you can get information on the possible advanced technics to get this behaviour without having an image in PNG format. For example, it is possible to halve your image in 2 JPEG images, one including the transparency data and the other one including the data related to the colours, and to gather the image on the customer's side with a CANVAS element.
For further information, please visit this article about image compression.
It seems that the PNG-8 format is the most suitable for the following images:
- seotools.com.np/theme/default/icons/[...]y_IP_address.png (11kB)
- seotools.com.np/theme/default/icons/[...]er_simulator.png (11kB)
- seotools.com.np/theme/default/icons/[...]ink_analyzer.png (11kB)
- https://seotools.com.np/theme/default/icons/google_cache.png (11kB)
- seotools.com.np/theme/default/icons/[...]in_authority.png (10kB)
It seems that the JPEG format is the most suitable for the following images:
1 critical dependency detected
The failure of a third-party content provider could bring an overall breakdown of your website.
Single Point Of Failure
A Frontend Single Point Of Failure (SPOF) is a critical dependency on a third-party content, that may block the entire display of your page in case of failure of the content provider.
As an example, if your web page uses a blocking script hosted by Google’s servers, then your page is reliant on any failure from this script. Please read this blog post dedicated to SPOF for more information.
How to avoid SPOF?
As far as possible, exclude any of these dependencies, even from renowned providers. If you have to use a third-party content, ensure that you choosed an asynchronous integration and that you have a fallback in case of problem.
We are checking if the tested web page depends (in a critical way) on some of most widespread external resources (googleapis, typekit,...). That are known as Frontend SPOF (Single Point Of Failure) cases.
This resource represents a SPOF for this page:
How can I fix this?
First of all, distinguish what portions of your JS is critical and must be loaded as soon as possible, and put them in a specific external file. Keep this file as streamlined as possible, and defer the parsing or execution of all other JS files (learn more).
- use the async attribute;
- use the defer attribute;
- make sure your scripts are placed at the bottom of the page (ideally at the end of the body).
Consider using jQuery 1.12
You webpage uses jQuery 1.10.2. You should migrate to the latest version of the 1.x branch: jQuery 1.12, that contains several bug and security fixes.
Should I migrate to the last version of jQuery ?
Migrating from a 1. x version of jQuery to the latest version (3.x) can have many unintended impacts and means losing compatibility with older browsers. You should only consider abandoning jQuery 1.x as a part of a complete overhaul of your Front-End infrastructure. As you reflect on it, you will surely discover that you might not need jQuery.
Did you know?
Your SSL certificate will expire on 05/05/2020. Update your certificate before that date.
What happens if my certificate expires?
Letting a certificate expire can have consequences for end users who will then see many error or alert messages while browsing the site, warning them of possible frauds, identity thefts or traffic interceptions. These alerts can have a very negative impact on the user's perception of the visited domain.
More informations about jQuery performance
1 domain sends 184 bytes of cookies
HTTP cookies are used to track a user to costumize the page according to their profile. They are sent as a HTTP header from the web server to the browser. Then, each time the browser accesses to the server, it sends a request containing the cookie received at the first response. See more information.
Here, 1 domain sends 184 bytes of cookies:
Domain name: yandex
i: 92 bytes distributed on 1 request(s)
yp: 54 bytes distributed on 1 request(s)
yabs-sid: 19 bytes distributed on 1 request(s)
yandexuid: 19 bytes distributed on 1 request(s)
This page does not load too much data (896kB)
A too high page weight slows down the display, especially on low speed connections. This can lead to frustration for users paying for data (see whatdoesmysitecost.com).
Evaluate the Weight of my Web Page
In February 2016, the average weight of 100 most visited websites in the world was 1,38MB.
How to reduce the weight of my page?
You can report to our "Data amount" category to discover the possible optimizations in your case. Images are often involved.
Moreover, make sure to build your web pages in order to load data that is essential to the user experience (rendering optimization of the critical path).
For other contents (social networking plugins, advertising, content at the bottom of the page ...), it is better to delay the loading (asynchronous, lazy-loading ...), so they don't override priority contents.
We strongly recommend that you define performance budgets before you carry out your web projects. These budgets can be settled through the Dareboost monitoring feature.
We have established the weight distribution of the page by resource type:
- Images : 60,08% of total weight
- Texts : 8,77% of total weight
- Font : 5,23% of total weight
- CSS : 5,14% of total weight
- JSON : 0,08% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- res.cloudinary.com/webtech/image/upl[...]9169/ads/ad3.png (92 kB)
- https://mc.yandex.ru/metrika/tag.js (88 kB)
- seotools.com.np/theme/default/fonts/[...]nt.woff2?v=4.6.3 (72 kB)
- ajax.googleapis.com/ajax/libs/jquery[...].2/jquery.min.js (33 kB)
- https://seotools.com.np/theme/default/css/theme.css (32 kB)
- https://seotools.com.np/theme/default/img/seobanner.png (29 kB)
- https://www.googletagmanager.com/gtag/js?id=UA-139890059-1 (25 kB)
- fonts.gstatic.com/s/lato/v15/S6uyw4B[...]UTPHjx4wXg.woff2 (24 kB)
- fonts.gstatic.com/s/lato/v15/S6u9w4B[...]h6UVSwiPGQ.woff2 (23 kB)
- https://www.google-analytics.com/analytics.js (18 kB)
This page contains 111 links
Two kind of links exist:
- Internal links that refer to pages with the same domain name;
- External links that point to other websites (must be relevant and point towards quality content).
If you reference many links, you can ask the SEO crawlers to consider only some of them, by adding the
rel=nofollow attribute to the irrelevant ones (e.g., advertisements).
Here is the distribution of 111 links present in the page:
- 108 internal links (97,30%)
- No "follow" external link (0,00%)
- 3 "nofollow" external links (2,70%)
Your server should be able to communicate with HTTP while it uses a HTTPS connection
Take precautionary measures against attacks like "man in the middle" by making sure to only communicate in HTTPS with the server.
The HTTP Strict Transport Security (HSTS) Header
When you communicate with a server through a secure connection, every sent request towards this server should use the HTTPS protocol. The HTTP HSTS header allows to indicate to the browser that all the requests sent to the domain concerned must be done via HTTPS. If the URL is presented under "http://...", the web browser is automatically going to replace it by "https://...".
However, we advise you to not set this header unless your entire website serves its resources in HTTPS.
For further information, you can read this article.
No HSTS header has been detected on this page.
Well done, these best practices are respected
Your HTML response is not too heavy
Why reduce the code amount of a page?
Before a web page can be displayed, the browser must, among other things, download it, parse it and model it into a document that can be understood by the rendering engine. If the amount of code contained in the page is too large, these steps are slowed down and the rendering is delayed.
How to reduce the amount of code?
Your HTML response should contain only the information that is immediately necessary to display the visible area of the page. Move inline information to external files (JS for scripts, CSS for styles, asynchronous queries for additional content) and simplify the HTML structure of your page.
No empty element detected
<quote> elements must not be empty because if they are, some screen readers will have difficulties interpreting their presence.
Remove these empty elements from you code or decorate them with the
aria-hidden attribute so that the screen readers ignore them.
You do not use too long inline scripts
Any script with a significant size should let the browser cached them in order to reduce loading time/improve performance of your returning visitor.
Inline scripts / cache policy
"inline" scripts allow to integrate easily small portions of scripts directly in the HTML code. Example:
ga('create', 'UA-11111111-1', 'mywebsite.com');
By doing so, you avoid making a request to the server to retrieve the resource. So inline scripts represent a performance gain if you want to integrate small scripts.
However, once a script has a fairly substantial size, we advise you to outsource it and perform a request to retrieve it. So you will benefit from the cache mechanism.
What should I do?
Outsource your scripts with more than 1500 characters in one or more separate files.
<noscript> tag detected
This page uses
This page defines <h1> and <h2> tags
We recommend putting page keywords in at least the h1 and h2 tags. Search engines use the h1, h2, and h3 tags for SEO purposes.
This page contains:
- 1 <h1> element(s)
- 3 <h3> element(s)
No frameset, frame and noframes tags detected
These tags are obsolete, due to several issues related to the navigation consistency, SEO or browsers' bookmark features for example.
None of these tags is detected on this page.
The use of the iframe tag is prefered.