Quality and Performance report

http://wpninjas.com
Report generated on Jul 12, 2016 5:31:43 PM

SIMULATED VISITOR: Chrome Washington DC 10.0/2.0Mbps (Latency: 28 ms) Edit

Requests

60

Weight

1.62MB

HTML CSS Scripts Images Others
Timeline / Waterfall

First Byte

0.06sec

Start Render

1.33sec

Fully loaded

1.37sec


Browser warnings 0OK
Speed Index: 1418

Technologies :

Backbone.js

Google Analytics

Google Font API

Twitter Emoji (Twemoji)

Underscore.js

WordPress

Yoast SEO

jQuery

PHP


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

Data amount 

0/100

17 images are resized with a width/height attribute

Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.

Resizing images explained

Using the width and height attributes in img tags is not recommended to reduce the rendering of an image.

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:

Don't resize the following images:


 
Read more
Browser rendering 

0/100

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 our 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:

  • //fonts.googleapis.com/css?family=Lato%3A300%2C7[...]%7CSpinnaker&ver=1440094952


 
Read more
Browser rendering 

0/100

Defer parsing of JavaScript

JavaScript can significantly slow down a page display, especially if it is necessary to download an external script.

Defer the use of JavaScript as much as possible to provide a faster start for the page display.

How can I fix this?

Use one of the methods below to defer parsing for external JavaScript files:

  • use the async attribute;
  • use the defer attribute;
  • append the script to the DOM in JavaScript during the onload event;
  • make sure your scripts are placed at the bottom of the page (ideally at the end of the body).

196.5KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.


 
Read more
Data amount 

0/100

Identical resources are served from different URLs

Resources with identical content should be served from the same URL to avoid duplicate downloads and additional requests.
You can save 1 requests and 17,52kB of data

Different URLs for the same resource

If you use different URLs to serve identical content, browsers have to request this content from the server several times, and your page will trigger unnecessary requests for data. If the same URL is used, the browser will only send one request and will use the response wherever the resource is requested. You should also use the same URL to reference the same content on several pages to benefit from the cache mechanism.

How to fix this?

Serve each resource from a unique URL. If you have to request the same resource several times, the same URL should be used to retrieve it every time.


The following URLs lead to identical content. Serve these resources from the same URL to save 1 request(s) and 17,52kB of data.


 
Read more
Data amount 

0/100

12 images (663kB) 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?

You can get informations concerning the features and plugins proposed by your page’s frameworks/CMS. You should find some easy-to-set solutions. Some Javascript libraries could help you to implement lazyloading too.

WordPress logoAs an exemple, with WordPress, you could install one of these extensions dedicated to images lazyloading.

12 images (663kB) loading can be delayed on this page, representing 49% of the total weight of all your images.


 
Read more
SEO 

0/100

Add <h1> title in your content

We recommend putting page keywords in at least the h1 and h2 tags. Search engines use the h1, h2, and h3 tags for SEO.
This page contains:

  • 14 <h2> element(s)


 
Read more

Did you know?

Browser rendering 

The Slowest Resources

The page load time is 1.4 seconds. Listed below, are your site's slowest loading requests:

Listed below, are your site's 10 slowest requests:

Excessively slow response times can be due to any number of reasons, usually because of a heavy resource that's loading or a temporary network issue.

For more information on page load time, you can consult the timeline.


 
Read more
Quality 

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.


 
Read more
Accessibility 

No <noscript> tag is detected

When a web page uses scripts, it is advised to set at least one noscript tag. It is required to display a message when JavaScript is disabled by the user.

<script  type="text/javascript">
document.write('Hello World!')
</script>
<noscript>Your browser does not support JavaScript!</noscript>


 
Read more
jQuery 

More informations about jQuery performance

jQuery is the most used JavaScript library. Upgrade your website performance respecting the jQuery best practices. We recommend that you learn the basics of the jQuery performance, reading the following link: http://learn.jquery.com/performance/.


 
Read more
Data amount 

This page does not load too much data (1,62 MB)

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 : 82,53% of total weight
  • JavaScript : 7,00% of total weight
  • CSS : 5,18% of total weight
  • Texts : 1,15% of total weight

Here is the weight of the 10 heaviest resources over the network, and that are necessary to load the page:


 
Read more

This page contains 6 links

Creating and then applying an efficient link strategy to your page will enhance its SEO.

Two main link types 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 algorithms to show interest in just some of them, adding the attribute rel=nofollow to the irrelevant ones (e.g., advertisements).

Here is the sharing distribution of 6 links present in the page:

  • 1 internal link (16,67%)
  • 5 "follow" external links (83,33%)
  • No "nofollow" external link (0,00%)


 
Read more

Well done, these best practices are respected

Cache policy 

100/100

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:

<script type="text/javascript">
    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']...,'/analytics.js','ga');
    ga('create', 'UA-11111111-1', 'dareboost.com');
</script>

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.


 
Read more
SEO 

100/100

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.


 
Read more
Compliance 

100/100

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.


 
Read more
SEO 

100/100

This page specifies a <title> tag

This page defines a title:

- WP Ninjas


 
Read more
Compliance 

100/100

No Java applets detected

Java applets are considered obsolete in 2015. HTML5 is powerful and more widely supported. Using Java applets can lead to compatibility issues and may send negative signals to your users (eg the browser indicating that content was blocked because it could be dangerous).

Congratulations, this page doesn't contain Java applets.


 
Read more
Compliance 

100/100

Do not use <bgsound> tag

No bgsound tag detected. This is a good practice: this element is not a HTML standard. See more information.

Use the audio tag to deliver audio content on your page.

<audio src="my-audio-file.ogg" autoplay>
Your browser doesn't support the audio element.
</audio>


 
Read more