3.8 sec in total
270 ms
3.1 sec
335 ms
Welcome to pharmatheque.com homepage info - get ready to check Pharmatheque best content right away, or after learning these important things about pharmatheque.com
Acheter et vendre votre Pharmacie avec les services juridico-financiers du leader en France : 32 délégués régionaux, + de 400 annonces en ligne.
Visit pharmatheque.comWe analyzed Pharmatheque.com page load time and found that the first response time was 270 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
pharmatheque.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value19.6 s
0/100
25%
Value12.4 s
3/100
10%
Value1,120 ms
23/100
30%
Value0.055
98/100
15%
Value19.4 s
2/100
10%
270 ms
678 ms
38 ms
191 ms
342 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 79% of them (62 requests) were addressed to the original Pharmatheque.com, 8% (6 requests) were made to Youtube-nocookie.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Pharmatheque.com.
Page size can be reduced by 283.0 kB (19%)
1.5 MB
1.2 MB
In fact, the total size of Pharmatheque.com main page is 1.5 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 693.1 kB which makes up the majority of the site volume.
Potential reduce by 28.9 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 28.9 kB or 78% of the original size.
Potential reduce by 8.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. Pharmatheque images are well optimized though.
Potential reduce by 245.0 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 245.0 kB or 35% of the original size.
Potential reduce by 624 B
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. Pharmatheque.com has all CSS files already compressed.
Number of requests can be reduced by 51 (75%)
68
17
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pharmatheque. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
pharmatheque.com
270 ms
www.pharmatheque.com
678 ms
icon
38 ms
materialize.min.css
191 ms
style.min.css
342 ms
media.min.css
332 ms
pharmatheque.min.css
393 ms
header.min.css
385 ms
banner.min.css
391 ms
footer.min.css
399 ms
actualites.css
501 ms
annonces.min.css
526 ms
cube_offre.css
556 ms
guide-transaction.min.css
600 ms
temoignages.css
600 ms
content.min.css
578 ms
nouislider.min.css
691 ms
jquery.realperson.css
725 ms
jquery.min.js
829 ms
jquery.realperson.min.js
827 ms
materialize.min.js
1163 ms
nouislider.min.js
828 ms
wNumb.js
876 ms
api.min.js
902 ms
highcharts.js
1003 ms
initialisation.min.js
1304 ms
acheter_pharmacie.min.js
1304 ms
actualites.min.js
1305 ms
connexion.min.js
1306 ms
contact.min.js
1306 ms
controlleur_saisie.min.js
1306 ms
cube_offre.min.js
1310 ms
deconnexion.min.js
1310 ms
detail_annonce.min.js
1311 ms
detail_annonce_connecte.min.js
1312 ms
guide_transaction.min.js
1340 ms
file_ariane.min.js
1353 ms
inscription.min.js
1384 ms
js
73 ms
mot_de_passe_oublie.min.js
1424 ms
profil.min.js
1233 ms
questionnaire.min.js
1100 ms
rechercher.min.js
1178 ms
temoignages.min.js
1141 ms
vendre_pharmacie.min.js
1239 ms
preparation_detail.min.js
1240 ms
recherche_avec_localisation.min.js
1235 ms
updateGeolocalisationAnnonce.js
1132 ms
ga.js
113 ms
zOrkxNSm9f8
184 ms
logo_background.png
986 ms
pharmatheque_logo_email.png
987 ms
facebook.svg
990 ms
twitter.svg
989 ms
in_logo.svg
994 ms
paris.jpeg
1444 ms
hero.jpg
1021 ms
Roboto-Bold.woff
1123 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf
39 ms
Roboto-Medium.woff
1148 ms
Roboto-Regular.woff
1176 ms
__utm.gif
23 ms
Roboto-Light.woff
1214 ms
Roboto-Thin.woff
1126 ms
www-player.css
8 ms
www-embed-player.js
30 ms
base.js
70 ms
moniteur_logo.png
1118 ms
asmjs.js
117 ms
Z-cpt7r5zEuZVquTy0XQyaNgKk5D9wurWQPuWSElJks.js
103 ms
embed.js
55 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
14 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
42 ms
Create
175 ms
IMG_1507-e1455200304485.jpg
444 ms
Cadre-legal-des-cessions-de-pharmacie.png
484 ms
141212-Pharmacie-CHABOT-Bordeaux.jpg
484 ms
GenerateIT
18 ms
pharmatheque.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
pharmatheque.com 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pharmatheque.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 uses legible font sizes
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pharmatheque.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Pharmatheque.com 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.
pharmatheque.com
Open Graph description is not detected on the main page of Pharmatheque. 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: