8.2 sec in total
199 ms
7 sec
942 ms
Welcome to greyline.com homepage info - get ready to check Greyline best content for India right away, or after learning these important things about greyline.com
Pulsar Measurement is a leading manufacturer of flow and level measurement products for water, wastewater, and industrial markets. With a wide range of technology in our portfolio, there is almost cer...
Visit greyline.comWe analyzed Greyline.com page load time and found that the first response time was 199 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
greyline.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value13.5 s
0/100
25%
Value17.8 s
0/100
10%
Value1,520 ms
13/100
30%
Value0.043
99/100
15%
Value37.9 s
0/100
10%
199 ms
1264 ms
86 ms
241 ms
221 ms
Our browser made a total of 286 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Greyline.com, 98% (279 requests) were made to Pulsarmeasurement.com and 1% (2 requests) were made to Bat.bing.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Pulsarmeasurement.com.
Page size can be reduced by 798.2 kB (15%)
5.4 MB
4.6 MB
In fact, the total size of Greyline.com main page is 5.4 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. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 146.5 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 146.5 kB or 88% of the original size.
Potential reduce by 23.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. Greyline images are well optimized though.
Potential reduce by 557.7 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 557.7 kB or 45% of the original size.
Potential reduce by 70.6 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. Greyline.com needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 28% of the original size.
Number of requests can be reduced by 236 (84%)
280
44
The browser has sent 280 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greyline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 193 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
greyline.com
199 ms
1264 ms
calendar.css
86 ms
styles-m.css
241 ms
slick.css
221 ms
cookieconsent.css
228 ms
overlay.css
233 ms
styles.css
234 ms
owl.carousel.min.css
233 ms
animate.css
294 ms
fontawesome5.css
377 ms
mgz_font.css
308 ms
mgz_bootstrap.css
309 ms
openiconic.min.css
309 ms
styles.css
316 ms
common.css
366 ms
styles.css
383 ms
magnific.css
385 ms
styles.css
386 ms
photoswipe.css
391 ms
default-skin.css
437 ms
blueimp-gallery.min.css
449 ms
styles.css
458 ms
autocomplete.css
460 ms
grid.css
462 ms
algolia-reset.css
467 ms
instantsearch.v3.css
509 ms
recommend.css
523 ms
customalgolia.css
534 ms
blog-m.css
536 ms
blog-new.css
537 ms
blog-custom.css
542 ms
styles-l.css
582 ms
bootstrap.min.css
672 ms
base.css
725 ms
site.css
612 ms
require.js
614 ms
js
70 ms
swap.js
31 ms
mixins.js
615 ms
requirejs-config.js
580 ms
cookieconsent.js
482 ms
bat.js
65 ms
close-icon.png
92 ms
dBi-M-Upgrade-Pop-Up-Banner.png
371 ms
close.svg
95 ms
logo.svg
98 ms
en.svg
96 ms
fr.svg
93 ms
farsight_-8_600px.jpg
171 ms
mdot_-21_600px.jpg
171 ms
pdfm-6.png
172 ms
reflect-radar-sensor.png
238 ms
sludge-finder-2-and-viper-transducer_1.png
312 ms
WES-Exhibiting-Blog-Post.png
462 ms
IFAT-380x380.png
236 ms
MicrosoftTeams-image_blog.jpg
390 ms
Asia_water_logo22.png
306 ms
PDFM-6.1_B_600px.png
312 ms
athens-blog-image.png
607 ms
mdot_wichita_blog_image.jpg
543 ms
reflect-covered-in-animal-feed.png
621 ms
FarSight_-16_600px.jpg
441 ms
in.svg
467 ms
yt.svg
515 ms
pulsar-footer-logos.png
538 ms
jquery.js
545 ms
common.js
588 ms
dataPost.js
612 ms
bootstrap.js
616 ms
app.js
621 ms
form-key-provider.js
658 ms
mage-translation-dictionary.js
676 ms
instantsearch.js
687 ms
insights.js
691 ms
theme.js
690 ms
main.js
696 ms
down.svg
700 ms
user.svg
721 ms
56002989.js
23 ms
modal-show.js
682 ms
SegoeUI.woff
847 ms
SegoeUI-Semibold.woff
686 ms
SegoeUI-Bold.woff
788 ms
SegoeUI-Black.woff
668 ms
search.svg
667 ms
next-white.svg
686 ms
domReady.js
708 ms
jquery-mixin.js
669 ms
pdfm_6-1-home_page_header_banner-new.jpg
702 ms
jquery.waypoints.js
634 ms
swirl.png
630 ms
next-orange.svg
650 ms
measurement.jpg
597 ms
icon-sprite.png
596 ms
quote.jpg
640 ms
power-generation.png
550 ms
fracking-holding-pools.png
544 ms
menu.svg
501 ms
phone.svg
495 ms
down-white.svg
518 ms
common.js
524 ms
template.js
474 ms
confirm.js
477 ms
widget.js
491 ms
main.js
515 ms
bootstrap.js
539 ms
types.js
539 ms
layout.js
508 ms
text.js
492 ms
smart-keyboard-handler.js
484 ms
mage.js
514 ms
slick.js
531 ms
bootstrap.bundle.min.js
541 ms
timeline.min.js
511 ms
jquery.rwdImageMaps.min.js
491 ms
wrapper.js
319 ms
player.js
198 ms
underscore.js
230 ms
translate.js
254 ms
modal.js
254 ms
version.js
236 ms
scripts.js
208 ms
knockout.js
632 ms
knockout-es5.js
634 ms
engine.js
631 ms
bootstrap.js
631 ms
observable_array.js
630 ms
bound-nodes.js
631 ms
main.js
627 ms
registry.js
626 ms
js-translation.json
624 ms
console-logger.js
623 ms
farsight--home-page-header-banner_option-b_1.jpg
90 ms
dbi-m-fm-approval-home-page-header-banner_amended.jpg
75 ms
radar_ultrasound-home_page_header_banner.png
160 ms
reflect-launch-banner.jpg
89 ms
lined-canal-banner.jpg
90 ms
sludge-tank-monitoring-header.jpg
151 ms
next.svg
147 ms
modal-popup.html
129 ms
modal-slide.html
130 ms
modal-custom.html
130 ms
key-codes.js
190 ms
core.js
195 ms
z-index.js
205 ms
knockout-repeat.js
185 ms
knockout-fast-foreach.js
186 ms
events.js
184 ms
local.js
240 ms
observable_source.js
239 ms
renderer.js
248 ms
resizable.js
250 ms
i18n.js
248 ms
scope.js
253 ms
range.js
303 ms
mage-init.js
312 ms
keyboard.js
324 ms
optgroup.js
324 ms
after-render.js
324 ms
autoselect.js
326 ms
datepicker.js
373 ms
outer_click.js
384 ms
fadeVisible.js
398 ms
collapsible.js
398 ms
staticChecked.js
400 ms
simple-checked.js
399 ms
bind-html.js
446 ms
tooltip.js
457 ms
color-picker.js
463 ms
arrays.js
459 ms
compare.js
461 ms
misc.js
457 ms
objects.js
444 ms
strings.js
456 ms
template.js
465 ms
logger.js
464 ms
entry-factory.js
466 ms
console-output-handler.js
466 ms
formatter.js
439 ms
message-pool.js
452 ms
levels-pool.js
464 ms
logger-utils.js
464 ms
data.js
465 ms
disable-selection.js
462 ms
focusable.js
442 ms
form.js
455 ms
ie.js
468 ms
keycode.js
468 ms
labels.js
468 ms
jquery-patch.js
466 ms
plugin.js
444 ms
safe-active-element.js
455 ms
safe-blur.js
468 ms
scroll-parent.js
469 ms
tabbable.js
468 ms
unique-id.js
468 ms
class.js
444 ms
async.js
455 ms
loader.js
468 ms
tooltip.html
407 ms
spectrum.js
392 ms
tinycolor.js
392 ms
entry.js
330 ms
moment.js
320 ms
dom-observer.js
101 ms
bindings.js
99 ms
magezon-builder.js
80 ms
loader.js
75 ms
page-cache.js
79 ms
google-analytics.js
80 ms
widget-initializer.js
80 ms
cookie-status.js
77 ms
cookies.js
115 ms
autocomplete.js
147 ms
block-loader.js
151 ms
section-config.js
154 ms
invalidation-processor.js
155 ms
customer-data.js
158 ms
customer-data-mixin.js
184 ms
customer-data-mixin.js
212 ms
authentication-popup.js
216 ms
loginCaptcha.js
219 ms
reCaptcha.js
219 ms
cookies.js
219 ms
cookie-settings.js
258 ms
customer.js
280 ms
storage-manager.js
288 ms
messages.js
293 ms
ui-messages-mixin.js
295 ms
messages.js
292 ms
disposable-customer-data-mixin.js
329 ms
parallax.js
332 ms
responsive-typography.js
342 ms
jquery.magnific-popup.min.js
352 ms
cookie-wrapper.js
275 ms
element.js
239 ms
block-loader.html
261 ms
url.js
276 ms
storage.js
287 ms
storage-wrapper.js
303 ms
cookie-setter.js
250 ms
form.js
245 ms
login.js
277 ms
authentication-popup.js
290 ms
alert.js
303 ms
validation.js
323 ms
captchaList.js
321 ms
collection.js
324 ms
registry.js
350 ms
reCaptchaScriptLoader.js
357 ms
nonInlineReCaptchaRenderer.js
373 ms
defaultCaptcha.js
395 ms
defaultCaptcha-mixin.js
395 ms
storage-service.js
329 ms
effect-blind.js
351 ms
escaper.js
352 ms
messageList.js
369 ms
cookie-decliner.js
359 ms
js.cookie.js
317 ms
links.js
310 ms
loader-1.gif
312 ms
js.storage.js
271 ms
cookie.js
288 ms
spinner.js
317 ms
resolver.js
316 ms
adapter.js
312 ms
jquery.validate.js
312 ms
captcha.js
233 ms
skipRefreshCaptcha.js
234 ms
data-storage.js
236 ms
ids-storage-compare.js
235 ms
ids-storage.js
232 ms
ids-storage-mixin.js
250 ms
effect.js
229 ms
messages.js
224 ms
api.js
40 ms
jquery.cookie.js
201 ms
recaptcha__en.js
22 ms
buttons.js
155 ms
refresh.js
80 ms
jquery.metadata.js
93 ms
query-builder.js
102 ms
jquery-var-for-color.js
87 ms
jquery.color.js
121 ms
print.css
79 ms
greyline.com 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
Links do not have a discernible 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.
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.
greyline.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
greyline.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 Greyline.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 Greyline.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.
greyline.com
Open Graph description is not detected on the main page of Greyline. 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: