6.2 sec in total
267 ms
3.6 sec
2.3 sec
Click here to check amazing PROMISE content for Netherlands. Otherwise, check out these important facts you probably never knew about promise.com
PROMISE Technology is a leading developer of high-performance storage solutions tailor-made for the data center, surveillance, cloud, and rich media markets. PROMISE specializes in providing the lates...
Visit promise.comWe analyzed Promise.com page load time and found that the first response time was 267 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
promise.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value18.2 s
0/100
25%
Value12.6 s
3/100
10%
Value400 ms
68/100
30%
Value0.521
15/100
15%
Value14.4 s
9/100
10%
267 ms
735 ms
511 ms
605 ms
327 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 84% of them (62 requests) were addressed to the original Promise.com, 5% (4 requests) were made to A1.mylivechat.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (848 ms) belongs to the original domain Promise.com.
Page size can be reduced by 955.3 kB (36%)
2.6 MB
1.7 MB
In fact, the total size of Promise.com main page is 2.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. 75% 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 119.3 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 20.7 kB, which is 14% 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 119.3 kB or 81% of the original size.
Potential reduce by 172.0 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. Obviously, PROMISE needs image optimization as it can save up to 172.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 380.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 380.7 kB or 68% of the original size.
Potential reduce by 283.2 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. Promise.com needs all CSS files to be minified and compressed as it can save up to 283.2 kB or 86% of the original size.
Number of requests can be reduced by 22 (32%)
68
46
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROMISE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
promise.com
267 ms
Index
735 ms
jquery-1.10.2.min.js
511 ms
jquery-ui-1.10.2.min.js
605 ms
jquery.carouFredSel-6.0.4-packed.js
327 ms
jquery.field.js
254 ms
jquery.hoverIntent.minified.js
245 ms
bootstrap.min.js
249 ms
jquery.prettyPhoto.js
323 ms
popwindow.js
320 ms
img_fade.js
328 ms
common.js
602 ms
script.js
602 ms
bootstrap.css
601 ms
prettyPhoto.css
601 ms
layout.css
848 ms
chatlink.aspx
219 ms
livechat.aspx
564 ms
livechat.aspx
526 ms
analytics.js
291 ms
jsml.js
317 ms
logo_fit.jpg
279 ms
chat_w.png
281 ms
arr_top_l.png
279 ms
FCJumpStart_773.jpg
311 ms
H_Banner_Pegasus2_R2.jpg
391 ms
H_Banner_VTrak.jpg
282 ms
PROMISE%20Technology%20Inc..png
280 ms
PR-CES.jpg
381 ms
AdobeAnywhere.png
296 ms
InterBEEE2015_180.jpg
293 ms
logo.png
381 ms
FileCruiser%202.0.jpg
380 ms
img_Kylie_Flavell_clear.jpg
562 ms
VTrak-J5000.png
381 ms
img_VosLogistics.jpg
561 ms
press-CCTV-Award.png
548 ms
Computex2015_Press.jpg
552 ms
press-BC-Award-R2-cover.jpg
547 ms
press-0416-NAB-2015-Award.jpg
547 ms
press_150410NAB.jpg
548 ms
img_VSky_H3970.jpg
549 ms
event-SecurityShow2016-180.jpg
548 ms
arr-b.png
549 ms
personal-cloud2.jpg
549 ms
arr-g.png
549 ms
ind_solutions_3.png
550 ms
ind_solutions_2.png
547 ms
arr-gr.png
681 ms
ind_solutions_4.png
678 ms
arr-o.png
678 ms
ind_solutions_1.png
678 ms
arr_left_d.png
678 ms
arr_right_d.png
693 ms
open_window.png
693 ms
linkin_l.png
692 ms
fb_l.png
692 ms
gtm.js
233 ms
collect
161 ms
resources.aspx
126 ms
twi_l.png
464 ms
youtube_l.png
462 ms
collect
117 ms
vibar.png
345 ms
dot.png
344 ms
right_tag_bg.png
377 ms
BackGround1.png
382 ms
Apollo_Index1920.jpg
587 ms
Index
633 ms
glyphicons-halflings-regular.woff
260 ms
conversion_async.js
28 ms
185 ms
chat_l.png
162 ms
488 ms
promise.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
List items (<li>) are not contained within <ul> or <ol> parent elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
promise.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
promise.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
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
EN
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Promise.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Chinese language. Our system also found out that Promise.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.
promise.com
Open Graph description is not detected on the main page of PROMISE. 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: