3.4 sec in total
453 ms
2.7 sec
211 ms
Welcome to bausch.pk homepage info - get ready to check Bausch best content right away, or after learning these important things about bausch.pk
Visit bausch.pkWe analyzed Bausch.pk page load time and found that the first response time was 453 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
bausch.pk performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.0 s
1/100
25%
Value12.4 s
3/100
10%
Value170 ms
92/100
30%
Value0
100/100
15%
Value6.7 s
57/100
10%
453 ms
431 ms
262 ms
445 ms
267 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 98% of them (83 requests) were addressed to the original Bausch.pk, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Bausch.pk.
Page size can be reduced by 199.2 kB (30%)
671.9 kB
472.7 kB
In fact, the total size of Bausch.pk main page is 671.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 409.4 kB which makes up the majority of the site volume.
Potential reduce by 18.2 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. This page needs HTML code to be minified as it can gain 5.2 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.2 kB or 78% of the original size.
Potential reduce by 18.4 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. Bausch images are well optimized though.
Potential reduce by 162.6 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 162.6 kB or 68% of the original size.
Number of requests can be reduced by 62 (74%)
84
22
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bausch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.bausch.pk
453 ms
styles.cssx
431 ms
styles.cssx
262 ms
jquery-1.7.2.min.js
445 ms
jquery.fancybox-1.3.4.min.js
267 ms
jquery.easing.1.2.js
180 ms
jquery.masonry.min.js
177 ms
jquery.jcarousel.min.js
266 ms
jquery.blockUI.js
354 ms
slides.min.jquery.js
349 ms
baulmb.main.js
357 ms
responsive.js
357 ms
VisitorIdentification.aspx
438 ms
sitetheme.cssz
441 ms
hor-bg.png
93 ms
bg.png
187 ms
vert-bg.png
104 ms
bauschLombLogoHome.jpg
104 ms
rightBorder.gif
104 ms
Pakistan-PAK.png
102 ms
downArrow.gif
141 ms
Argentina-ARG.png
213 ms
Australia-AUS.png
213 ms
Austria-AUT.png
210 ms
Belgium-BEL.png
212 ms
Brazil-BRA.png
233 ms
Bulgaria-BGR.png
279 ms
Canada-CAN.png
317 ms
China-CHN.png
324 ms
Czech-Republic.png
315 ms
Denmark-DEN.png
316 ms
Estonia-EST.png
327 ms
Finland-FIN.png
374 ms
France-FRA.png
434 ms
Germany-DEU.png
432 ms
Greece.png
473 ms
Hong-Kong-HKG.png
480 ms
Hungary-HUN.png
471 ms
India-IND.png
490 ms
Indonesia-IDN.png
524 ms
Ireland-IE.png
534 ms
Italy-ITA.png
585 ms
Japan-JPN.png
603 ms
South-Korea-KOR.png
623 ms
lativa-LVA.png
623 ms
Lithuania-LTU.png
641 ms
Malaysia-MYS.png
644 ms
Mexico-MEX.png
678 ms
Netherland-NLD.png
702 ms
NewZeland-NZL.png
721 ms
ga.js
30 ms
__utm.gif
12 ms
Norway-NOR.png
653 ms
Pakistan-PAK.png
662 ms
Philippines.png
662 ms
Poland-POL.png
677 ms
Romania-ROU.png
721 ms
Russia-RUS.png
744 ms
Singapore-SGP.png
708 ms
Slovakia-SVK.png
693 ms
South-Africa-ZAF.png
701 ms
Spain-ESP.png
691 ms
Sweden-SWE.png
705 ms
Switzerland-CHE.png
745 ms
Taiwan-TWN.png
707 ms
Turkey-TUR.png
680 ms
Ukraine-UKR.png
679 ms
UnitedKingdom-UK.png
684 ms
United%20States%20of%20America.png
685 ms
1x1-pixel.png
738 ms
mainNavBg.png
697 ms
bl-mission.png
1175 ms
arrow-prev.png
651 ms
arrow-next.png
619 ms
akreos-mics.jpg
627 ms
mainNavDivider.png
671 ms
megaDropDownMid.png
667 ms
megaDropDownBtm.png
645 ms
megaDropDownTop.png
645 ms
carousel-left.png
610 ms
carousel-center.png
635 ms
carousel-right.png
620 ms
btnArrow.png
633 ms
homePromoBoxContainerBg.png
624 ms
footerBG.png
630 ms
bausch.pk 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
Image elements do not have [alt] attributes
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.
bausch.pk 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
bausch.pk SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bausch.pk can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Bausch.pk 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.
bausch.pk
Open Graph description is not detected on the main page of Bausch. 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: