1.5 sec in total
153 ms
952 ms
430 ms
Visit flowserveflex.com now to see the best up-to-date Flowserve Flex content and also check out these interesting facts you probably never knew about flowserveflex.com
Flowserve moves, controls and protects the flow of materials in the world's most critical industries. Contact a representative today to learn more.
Visit flowserveflex.comWe analyzed Flowserveflex.com page load time and found that the first response time was 153 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
flowserveflex.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value9.6 s
0/100
25%
Value7.4 s
27/100
10%
Value1,480 ms
14/100
30%
Value0.205
60/100
15%
Value10.7 s
22/100
10%
153 ms
53 ms
48 ms
55 ms
90 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Flowserveflex.com, 10% (10 requests) were made to Flowserve.widen.net and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (376 ms) relates to the external source Flowserve.com.
Page size can be reduced by 289.4 kB (42%)
687.8 kB
398.4 kB
In fact, the total size of Flowserveflex.com main page is 687.8 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. 70% of websites need less resources to load. Javascripts take 264.4 kB which makes up the majority of the site volume.
Potential reduce by 217.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 217.6 kB or 83% of the original size.
Potential reduce by 0 B
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. Flowserve Flex images are well optimized though.
Potential reduce by 39.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 39.0 kB or 15% of the original size.
Potential reduce by 32.8 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. Flowserveflex.com needs all CSS files to be minified and compressed as it can save up to 32.8 kB or 24% of the original size.
Number of requests can be reduced by 73 (78%)
94
21
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flowserve Flex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
153 ms
google_tag.script.js
53 ms
mp_linkcode.js
48 ms
motionpoint-language-selector.css
55 ms
align.module.css
90 ms
container-inline.module.css
96 ms
hidden.module.css
89 ms
eu_cookie_compliance.bare.css
95 ms
addtoany.css
96 ms
extlink.css
100 ms
font-awesome.min.css
100 ms
tb_megamenu.bootstrap.css
115 ms
tb_megamenu.base.css
121 ms
tb_megamenu.default.css
137 ms
tb_megamenu.compatibility.css
124 ms
site-footer.css
159 ms
skip-link.css
135 ms
bootstrap.min.css
127 ms
main.css
140 ms
card-grid.css
159 ms
video-gallery.css
163 ms
card-slider.css
165 ms
slick.css
101 ms
carousel-slider.css
167 ms
global-search-auto-complete.css
171 ms
drupalSettingsLoader.js
238 ms
drupal.js
172 ms
drupal.init.js
173 ms
condition_type.standard.js
172 ms
condition.browser.js
181 ms
condition.common.js
206 ms
OtAutoBlock.js
122 ms
otSDKStub.js
133 ms
polyfill.min.js
163 ms
jquery.min.js
185 ms
quicklink.umd.js
109 ms
once.min.js
184 ms
debounce.js
195 ms
quicklink_init.js
198 ms
index.umd.min.js
208 ms
page.js
110 ms
addtoany.js
209 ms
datalayer.js
212 ms
lazy.js
213 ms
bootstrap.bundle.min.js
95 ms
slick.min.js
91 ms
mpel.js
92 ms
odometer.js
92 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
159 ms
barrio.js
218 ms
affix.js
375 ms
global.min.js
376 ms
mainmenuoverride.min.js
369 ms
extlink.js
333 ms
js.cookie.min.js
335 ms
eu_cookie_compliance.min.js
328 ms
widen_display.js
327 ms
lazysizes.min.js
329 ms
ls.respimg.min.js
326 ms
ls.parent-fit.min.js
307 ms
ls.blur-up.min.js
303 ms
ls.object-fit.min.js
303 ms
videoGallery.min.js
309 ms
cardSlider.min.js
309 ms
css
44 ms
css2
56 ms
progress.js
291 ms
loadjs.min.js
323 ms
announce.js
319 ms
message.js
315 ms
ajax.js
312 ms
smart_content.js
312 ms
carouselSlider.min.js
308 ms
globalSearchAutoComplete.min.js
346 ms
customJs.js
343 ms
3df5f69c-a4ed-4173-9a88-f9347e951862.json
158 ms
blurred-energy-transition-hero-1440x900-2x.webp
245 ms
logo.svg
191 ms
Login.svg
193 ms
Burgermenu.svg
195 ms
close.svg
195 ms
Right.svg
225 ms
Left.svg
224 ms
play.svg
220 ms
play_hover.svg
221 ms
CS102-20_Still_004.webp
277 ms
AdobeStock_556745297_flipped.webp
222 ms
industrial-blue.webp
249 ms
AdobeStock_294827158.webp
279 ms
fls-cares-bali-child-drinking-2x.webp
274 ms
toys-tots.webp
303 ms
AdobeStock_205533357.webp
304 ms
location
143 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSyccg.ttf
87 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EiSysdUmj.ttf
97 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1Euyyccg.ttf
115 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EuyysdUmj.ttf
127 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yyccg.ttf
128 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1E1yysdUmj.ttf
129 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1Ebiuccg.ttf
128 ms
NGSpv5_NC0k9P_v6ZUCbLRAHxK1EbiusdUmj.ttf
129 ms
fontawesome-webfont.woff
69 ms
blurred-energy-transition-hero-1440x900-2x.webp
59 ms
blurred-energy-transition-hero-1440x900-2x.webp
90 ms
flowserveflex.com 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
[aria-*] attributes do not match their roles
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
Heading elements are not in a sequentially-descending order
flowserveflex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
flowserveflex.com 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flowserveflex.com 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 Flowserveflex.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.
flowserveflex.com
Open Graph description is not detected on the main page of Flowserve Flex. 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: