2.7 sec in total
107 ms
2.4 sec
240 ms
Click here to check amazing FRONTLINE content for France. Otherwise, check out these important facts you probably never knew about frontline.fr
FRONTLINE est une marque de médicaments vétérinaires et de produits dédiés à la santé des chiens et des chats.
Visit frontline.frWe analyzed Frontline.fr page load time and found that the first response time was 107 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
frontline.fr performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value4.3 s
42/100
25%
Value3.8 s
84/100
10%
Value1,660 ms
11/100
30%
Value0.003
100/100
15%
Value8.9 s
35/100
10%
107 ms
158 ms
956 ms
96 ms
15 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 59% of them (41 requests) were addressed to the original Frontline.fr, 37% (26 requests) were made to Global.frontline.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (956 ms) belongs to the original domain Frontline.fr.
Page size can be reduced by 718.9 kB (35%)
2.0 MB
1.3 MB
In fact, the total size of Frontline.fr main page is 2.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 56.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 56.4 kB or 75% of the original size.
Potential reduce by 24.5 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. FRONTLINE images are well optimized though.
Potential reduce by 313.4 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 313.4 kB or 72% of the original size.
Potential reduce by 324.5 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Frontline.fr needs all CSS files to be minified and compressed as it can save up to 324.5 kB or 87% of the original size.
Number of requests can be reduced by 41 (64%)
64
23
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FRONTLINE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
frontline.fr
107 ms
www.frontline.fr
158 ms
default.aspx
956 ms
init.js
96 ms
ScriptResource.axd
15 ms
blank.js
6 ms
ScriptResource.axd
13 ms
v5.js
5 ms
controls.css
6 ms
Menu.css
7 ms
search.css
10 ms
corev4.css
56 ms
v5.css
11 ms
responsivechild.css
15 ms
respond.src.js
48 ms
jquery.min.js
47 ms
WebResource.axd
27 ms
global.js
17 ms
ga.js
91 ms
fr.png
134 ms
dk.png
68 ms
bg.png
79 ms
hr.png
67 ms
tr.png
79 ms
il.png
79 ms
se.png
85 ms
ar.png
87 ms
be.png
93 ms
pl.png
91 ms
cy.png
89 ms
fi.png
87 ms
es.png
103 ms
hu.png
103 ms
nz.png
104 ms
nl.png
104 ms
ru.png
101 ms
pt.png
103 ms
ro.png
120 ms
rs.png
121 ms
ch.png
122 ms
si.png
118 ms
za.png
118 ms
in.png
119 ms
gb.png
133 ms
logo_sml.png
134 ms
sanofi-logo.jpg
10 ms
frontline-brand-products-logo.png
131 ms
dropdown.jpg
918 ms
search.jpg
57 ms
gosearch15.png
32 ms
bgximg.png
41 ms
carousel_nav.png
171 ms
carousel_arrow_prev.png
53 ms
carousel_arrow_next.png
79 ms
Banniere01.jpg
71 ms
Banniere02.jpg
72 ms
Banniere03.jpg
74 ms
Banniere04.jpg
75 ms
Banniere05.jpg
75 ms
shadow.jpg
83 ms
illu_pense_bete1.png
80 ms
10_88x55.jpg
92 ms
fleche.png
83 ms
09_88x55.jpg
84 ms
footer_block_risks.jpg
85 ms
image2-droite.png
86 ms
btn-btt.png
154 ms
footer-logo.png
87 ms
footprints.png
88 ms
__utm.gif
16 ms
frontline.fr accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
frontline.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
frontline.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document doesn't use legible font sizes
Tap targets are not sized appropriately
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frontline.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Frontline.fr main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
frontline.fr
Open Graph description is not detected on the main page of FRONTLINE. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: