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
9 images are resized on browser side
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
Don't resize the following images:
- https://newyorkstyle.pl/images/logo-biale.png (displayed size: 158x140)
- https://newyorkstyle.pl/images/fb1.png (displayed size: 30x30)
- https://newyorkstyle.pl/images/pinterest.png (displayed size: 30x30)
- newyorkstyle.pl/produkty/15[...]36-min.jpg (displayed size: 133x200)
- newyorkstyle.pl/produkty/15[...]10-min.jpg (displayed size: 133x200)
- newyorkstyle.pl/produkty/15[...]40-min.jpg (displayed size: 133x200)
- https://newyorkstyle.pl/images/instagram.png (displayed size: 30x30)
- newyorkstyle.pl/produkty/15[...]62-min.jpg (displayed size: 150x200)
- newyorkstyle.pl/produkty/15[...]36-min.jpg (displayed size: 133x200)
On this page, 5 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:
- https://newyorkstyle.pl/images/cookie_yes.png (displayed size: 20x20)
- https://newyorkstyle.pl/images/box2.jpg (displayed size: 387x252)
- https://newyorkstyle.pl/images/box1.jpg (displayed size: 387x252)
- https://newyorkstyle.pl/images/box3.jpg (displayed size: 387x252)
- https://newyorkstyle.pl/images/box4.jpg (displayed size: 804x415)
Optimize your images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 81.0KiB (25% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].png could save 17.0KiB (29% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].jpg could save 15.0KiB (72% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].jpg could save 11.9KiB (42% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].jpg could save 11.4KiB (41% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].png could save 3.9KiB (39% reduction).
- Losslessly compressing newyorkstyle.pl/pr[...].jpg could save 3.5KiB (14% reduction).
- Losslessly compressing newyorkstyle.pl/pr[...].jpg could save 3.3KiB (14% reduction).
- Losslessly compressing newyorkstyle.pl/pr[...].jpg could save 3.2KiB (13% reduction).
- Losslessly compressing newyorkstyle.pl/pr[...].jpg could save 2.9KiB (13% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].png could save 2.5KiB (85% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].png could save 2.4KiB (79% reduction).
- Losslessly compressing newyorkstyle.pl/im[...].png could save 2.4KiB (78% reduction).
- Losslessly compressing newyorkstyle.pl/pr[...].jpg could save 1.7KiB (3% reduction).
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:
How can I fix this?
- 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.7.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.
11 images (297kB) 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 example, with jQuery you could use a plugin dedicated to images lazyloading.
11 images (297kB) loading can be delayed on this page, representing 38% of the total weight of all your images.
Did you know?
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.
1 domain sends 2kB 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 2kB of cookies:
Domain name: newyorkstyle
PHPSESSID: 988 bytes distributed on 38 request(s)
_gid: 351 bytes distributed on 13 request(s)
_ga: 338 bytes distributed on 13 request(s)
_gat_gtag_UA_113949975_1: 13 bytes distributed on 13 request(s)
4 resources on this page are for public use
By default, the browser accepts to perform AJAX requests, or to retrieve web fonts, only on the same domain name of the page. So a font provided by toto.com can only be used by the pages of toto.com. This prevents misuse of your resources by any site.
Some resources are public, and explicitly want to be available to everyone (eg Google Fonts). In this case, the HTTP header
Access-Control-Allow-Origin can be used with the value "*". You should, however, use this property if your resource has aimed to be used by the greatest number. Otherwise, we recommend that you keep the default, or set a specific domain name in the "Access-Control-Allow-Origin" HTTP header.
You should be aware of the following resources, that use a
Access-Control-Allow-Origin: * HTTP header. Make sure they are actually intended to be used by pages from all domain names:
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.
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
Do all third parties resources deliver the right content?
This page loads data from third parties, you should ensure their integrity.
SubResource Integrity (SRI)
Use SRI to ensure that a third party resource has not been tampered. Add the
integrity attribute to
<link> tags loading this kind of resource. Example:
integrity attribute value is equal to the base64-encoded hash (SHA) of the resource. The browser compares this hash with the downloaded content in order to determine if the resource matches the expected content.
You can create the SHA thanks to several tool. In command line, you can use openssl. You can also test some online tools, as srihash.org or report-uri.io. Learn more about SubResource Integrity.
Well done, these best practices are respected
Your font formats are well used
Be sure to deliver the most suitable font format for each platform.
Declaring several font formats
The web browsers (Firefox, Chrome, Safari, Internet Explorer, Opera ...) do not support all the same font formats. Your goal is to use the lightest possible format for each platform. When you use a font, you can specify several formats, via the @font-face CSS instruction: so the browser will use the first compatible format that it supports.
How to declare your font formats?
Check if your formats are well ordered in the
src property. Here's an article about this topic to help you to determine the right order to declare your fonts. TL; DR order to respect for your webfont formats: EOT, WOFF2, WOFF, TTF, and SVG.
All fonts are well ordered in the
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.
You have defined a <meta> 'description'
The page should define a unique description.
Description in search engines
The description of the page may be directly displayed in search engine results pages (SERP):
It allows you to control at best the entry preview in search engines, and to improve the click rate to your page. Learn more.
How to define a page's description?
<meta name="description" content="page description"> and place it in the
This page defines one <meta>
Sklep internetowy New York Style oferuje wysokiej jakości odzież ciążową oraz odzież do karmienia. W naszej ofercie znajdują się również najnowsze kolekcje odzieży dziecięcej marek Sofija I Ewa Collection.
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.
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 specifies a <title> tag
The page should define a unique title (using a <title> tag).
Use of titles by search engines
Once properly configured, the page title can be displayed in the search engine results page:
Using a suitable title is a major criterion for SEO. It allows you to control at best what is displayed in search results pages, and determine the keywords you want your site pops out.
How to define the title of a web page?
The title of the page is specified into the
<title> tag, which must be placed into the
<head> tag, at the beginning of the code.
This page defines a title the
Here is the page's title:
New York Style: ubrania ciążowe, ubrania do karmienia - sklep internetowy