Quality and Performance reporthttps://www.gratispsncodes.online/free-psn-codes-psn-code-generator/
Report generated on Jan 23, 2019 9:50:18 AM
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
This page is exposed to the Mixed Content issue
This page uses the HTTPS protocol, so for security purpose, all resources should be retrieved via HTTPS. Nevertheless, we have detected resources requested over simple HTTP. Such resources are called Mixed Contents. Mixed Contents are generally blocked by web browsers to prevent security issues.
The following resources are Mixed Contents:
Some browsers will no more mark your website as secure. Here is the impact of the mixed content issue on Chrome 55:
Worse, the browser will block the resources concerned if it considers they can interact with the page (scripts, css, iframes, etc). To avoid an attack, you should strongly consider solving this issue.
For further information on Mixed Content, you can read this article on this subject.
3 resources are unreachable
You should avoid requesting unreachable resources.
Warning notifications that some requests related to your page are encountering errors can be due to:
- an unhandled error on the server side;
- or a problem on a service used by your page.
The following HTTP codes were returned:
- 403 ():
These errors can affect content on and behaviors of your website and cause unnecessary network traffic, which affects the loading time of your page.
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).
8 images (343kB) are loaded too early
Load images above the foldline first, that means all the images that are visible without any scroll of the page by the visitor.
Webpage and images
Images use to represent more than 60% of the total weight of webpages. By loading initially the only images that are visible without page scrolling, you’ll reduce bandwith consumption as for your server and your visitors. If an image has to display after any visitor’s action (as scrolling) , then you’d better load it on demand, when necessary (lazyloading).
How to set up lazyloading?
As an exemple, with WordPress, you could install one of these extensions dedicated to images lazyloading.
8 images (343kB) loading can be delayed on this page, representing 64% of the total weight of all your images.
Save 8 requests using CSS sprites
Combining images into CSS sprites reduces the number of files the browser has to download and accelerates the loading time.
CSS sprites explained
A CSS sprite is a single file in which several smaller images are grouped and positioned one beside the other. You can display each small image in your page by applying CSS styles, and a single request is necessary to recover all the images. Use this method only for small images, such as icons, so the CSS sprite is not too heavy.
Here is a CSS sprite example :
The page also applies the styles associated with the sprite:
background-position: -74px 0;
Then you have just to define the right class in your HTML file, and the icon appears:
<span class="sprite sprite-browsers-firefox"></span>
How should I create CSS sprites?
Their creation can be complex, so we recommend using tools that easily generate them for you. Here are a few sprite generators:
9 can be combined in a CSS sprite. The domain name livetrafficfeed should use this technique for the following resources:
Did you know?
Your SSL certificate will expire on 04/23/2019. 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.
No HTML code is commented
Comments allow you to detail a portion of code and help you navigate more efficiently in the DOM. However, make sure no sensitive information is exposed in your comments.
Well done, none of your comments contains HTML code.
More informations about jQuery performance
1 domain sends 338 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 338 bytes of cookies:
Domain name: livetrafficfeed
PHPSESSID: 338 bytes distributed on 13 request(s)
You serve scaled images
Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.
Resizing images explained
Resizing images on browser side to reduce their rendering size is not recommended.
For instance, if your image is set to render at 300px by 300px on a particular page, don't upload the original 1000px by 1000px version of that image to your page. Instead, resize/crop the image to fit the display size and then upload it to your site to decrease the page weight and loading time.
Using images with responsive designs or retina screens?
Responsive website designs and retina screens do not justify an image resizing. Even in such cases, some methods exist to deliver your pictures to the right size. We recommend reading the following resources:
- Introduction to responsive images
- Picturefill, to start using the <picture> element
- RICG, group of developers working on responsive images
Good job! No image resize have been detected. This is ideal for reducing page weight and loading time.
On this page, 3 images are resized by less than 35%. This can be consistent in a Responsive Web Design website, so this best practice does not penalize the following resources, but please make sure that they do not affect the page performance:
This page does not load too much data (1.1MB)
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 : 50,08% of total weight
- Font : 10,55% of total weight
- Texts : 2,56% of total weight
- CSS : 2,53% of total weight
Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:
- www.gratispsncodes.online/newimages/[...]rds-for-free.png (217 kB)
- www.gratispsncodes.online/newimages/[...]n-codes-free.jpg (119 kB)
- pagead2.googlesyndication.com/pagead[...]show_ads_impl.js (72 kB)
- https://www.gratispsncodes.online/newimages/freepsncodes.jpg (50 kB)
- ssl.microsofttranslator.com/ajax/v3/[...]s=Manual&from=en (47 kB)
- www.gratispsncodes.online/wp-content[...]/images/logo.png (44 kB)
- www.gratispsncodes.online/newimages/[...]sit-site-now.gif (40 kB)
- https://www.googletagmanager.com/gtag/js?id=UA-118180573-3 (34 kB)
- www.gratispsncodes.online/wp-include[...]ry.js?ver=1.12.4 (33 kB)
- https://ssl.bing.com/widget/metrics.js (33 kB)
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.
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)
- 8 <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.
This page uses only standard image formats
The images that use a non-standard format may not be indexed by search engines.
Only these image formats are considered standard on the web: jpeg, jpg, png, gif, svg, ico, webp. You should consider an alternative to any other format.
Moreover, remember to treat the text around your images: some search engines analyze approximately the 10 words preceding and following the image in order to add a context to the image.