4.2 sec in total
196 ms
2.7 sec
1.3 sec
Welcome to pfizer.be homepage info - get ready to check Pfizer best content for Belgium right away, or after learning these important things about pfizer.be
Homepage
Visit pfizer.beWe analyzed Pfizer.be page load time and found that the first response time was 196 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pfizer.be performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value11.1 s
0/100
25%
Value8.0 s
22/100
10%
Value880 ms
32/100
30%
Value0.166
71/100
15%
Value10.7 s
22/100
10%
196 ms
207 ms
442 ms
123 ms
222 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 82% of them (36 requests) were addressed to the original Pfizer.be, 11% (5 requests) were made to Cookies.pfizer.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pfizer.be.
Page size can be reduced by 762.9 kB (21%)
3.6 MB
2.8 MB
In fact, the total size of Pfizer.be main page is 3.6 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. 35% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 39.6 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 39.6 kB or 82% of the original size.
Potential reduce by 63.8 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. Pfizer images are well optimized though.
Potential reduce by 478.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 478.6 kB or 70% of the original size.
Potential reduce by 181.0 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. Pfizer.be needs all CSS files to be minified and compressed as it can save up to 181.0 kB or 84% of the original size.
Number of requests can be reduced by 16 (39%)
41
25
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pfizer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
pfizer.be
196 ms
www.pfizer.be
207 ms
nl-be
442 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
123 ms
css_yUpyqlogowusI_jASJahF2GcJrj0FHdyzhsrm2IRAOk.css
222 ms
css_ctmKxZuFFA3WUFzG1AgdVH86O2P0jeYh_bg8-B7Djds.css
251 ms
www-pfizer-be-nl.css
432 ms
css_lEwDL9fwW88IGNGPK9BiYBScfQ3WPnxZlXEOmg6MtF4.css
329 ms
js_JE9pq6eEWLckDlN4xJceut6LfFPHXWJ4gPnaBUlptTw.js
320 ms
js_rrwXgzzg8cTBuJ4hwfYVT05zUoF4wg-T1hb3FaYXWAc.js
248 ms
js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js
249 ms
js_WqfNugpiuKMxFXfrgHDgO6J_VmLtfliAgGEZL7lRKA0.js
311 ms
seckit.document_write.js
327 ms
seckit.no_body.css
342 ms
js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js
342 ms
js_sdNmlZF7h_FqNIXgAByInmkFh0IctPrb5ImWt__t5UA.js
410 ms
www-pfizer-be-nl.js
681 ms
js_-Fnt8Uzcr0CUWwGNCNqQo4n8WkHRzuwLQxovkGi6ho0.js
416 ms
s_code.js
490 ms
js_7Ukqb3ierdBEL0eowfOKzTkNu-Le97OPm-UqTS5NENU.js
421 ms
analytics.js
23 ms
collect
12 ms
pfizer-focus.jpg
305 ms
img-menu-who-is-pfizer_0.jpg
304 ms
pfizer-partners_6.jpg
231 ms
pfizer-products_0.jpg
238 ms
jobs-at-pfizer_1_0.jpg
233 ms
logo-pfizer-footer.png
124 ms
homepage.jpg
388 ms
logo.png
312 ms
section-blog_0.png
307 ms
image001.png
541 ms
120150920anemones20photo20peinture20veronique.jpg
371 ms
geen_chemistry-square.jpg
454 ms
rsz_1rsz_1pfizer_in_belgium_4.jpg
1065 ms
pfizer_products_0_0.jpg
616 ms
jobs-at-pfizer.jpg
448 ms
pfizer-partners.jpg
540 ms
pfizer-focus.jpg
599 ms
corner-l.png
78 ms
c-star.png
78 ms
ui-bg_flat_100_008fd5_40x100.png
133 ms
fontawesome-webfont.woff
490 ms
s56272543135564
40 ms
pfizer.be accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
pfizer.be 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
pfizer.be 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 uses legible font sizes
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pfizer.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pfizer.be 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.
pfizer.be
Open Graph description is not detected on the main page of Pfizer. 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: