7.1 sec in total
1.1 sec
5.8 sec
209 ms
Click here to check amazing Pelecard content for Israel. Otherwise, check out these important facts you probably never knew about pelecard.com
פלאקארד – 20 שנות נסיון סליקת כרטיסי אשראי. סליקה מאובטחת עם תקן PCI לארגונים, עסקים קטנים, אתרי אינטרנט, קופות. עם מערכת בקרה וממשק מלא למערכות ניהול.
Visit pelecard.comWe analyzed Pelecard.com page load time and found that the first response time was 1.1 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pelecard.com performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.4 s
0/100
25%
Value10.5 s
7/100
10%
Value1,410 ms
16/100
30%
Value0.016
100/100
15%
Value11.6 s
18/100
10%
1050 ms
311 ms
633 ms
313 ms
327 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 37% of them (52 requests) were addressed to the original Pelecard.com, 11% (16 requests) were made to Googleadservices.com and 11% (15 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Site.blabla4u.com.
Page size can be reduced by 499.9 kB (45%)
1.1 MB
605.1 kB
In fact, the total size of Pelecard.com main page is 1.1 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. 45% of websites need less resources to load. Javascripts take 535.0 kB which makes up the majority of the site volume.
Potential reduce by 50.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 6.9 kB, which is 11% 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 50.3 kB or 83% of the original size.
Potential reduce by 41.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. Pelecard images are well optimized though.
Potential reduce by 384.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 384.6 kB or 72% of the original size.
Potential reduce by 24.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. Pelecard.com needs all CSS files to be minified and compressed as it can save up to 24.0 kB or 83% of the original size.
Number of requests can be reduced by 64 (61%)
105
41
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pelecard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.pelecard.com
1050 ms
AllSitesStyle_RTL.css
311 ms
jquery-1.7.2.min.js
633 ms
ui.totop.css
313 ms
easing.js
327 ms
jquery.ui.totop.js
322 ms
c_config_RTL.js
331 ms
clientFunctions.js
461 ms
JSFunctions.js
464 ms
swfobject.js
480 ms
c_smartmenus.js
493 ms
tools.flashembed-1.0.4.min.js
495 ms
thickbox.js
612 ms
loadCommentsFAQ.js
617 ms
screen_RTL.css
651 ms
jquery.metadata.js
658 ms
jquery.validate.js
657 ms
cmxforms.js
762 ms
validateFunc.js
769 ms
jquery.scrollbox.js
782 ms
demo.css
793 ms
RTLnf.lightbox.css
1130 ms
RTLNFLightBox.js
821 ms
mobile.js
912 ms
awesome.css
920 ms
style.css
932 ms
flaticon.css
951 ms
conversion.js
33 ms
safe-standard.js
33 ms
reset.css
337 ms
core.css
415 ms
cmxformTemplate.css
425 ms
cmxform_RTL.css
436 ms
ga.js
29 ms
hotjar-31186.js
127 ms
29 ms
online-1494045868.png
26 ms
logo-pelecard.png
1039 ms
info.jpg
179 ms
pelecard-pci-level-180X134.jpg
314 ms
teura.jpg
173 ms
tau.jpg
168 ms
toto.png
330 ms
isrotel%20logo.jpg
331 ms
macabi2.png
331 ms
tlv.jpg
354 ms
egged.png
666 ms
leumi.jpg
489 ms
credit.jpg
486 ms
65 ms
66 ms
67 ms
71 ms
69 ms
73 ms
73 ms
75 ms
76 ms
78 ms
78 ms
89 ms
default.aspx
810 ms
bg_tools.jpg
466 ms
bg3.jpg
505 ms
bg2.jpg
625 ms
bg4.jpg
618 ms
bg_customer.jpg
629 ms
bg_content.jpg
691 ms
48 ms
safe-standard.js
73 ms
inpage_linkid.js
28 ms
116 ms
line_footer.jpg
729 ms
57 ms
55 ms
54 ms
52 ms
61 ms
81 ms
54 ms
48 ms
55 ms
53 ms
48 ms
74 ms
64 ms
safe-standard.js
54 ms
__utm.gif
44 ms
99 ms
55 ms
54 ms
60 ms
56 ms
53 ms
52 ms
86 ms
69 ms
83 ms
81 ms
fbds.js
65 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
71 ms
ui_totop.png
654 ms
loadingAnimation.gif
677 ms
63 ms
60 ms
collect
99 ms
likebox.php
416 ms
75 ms
108 ms
46 ms
37 ms
53 ms
visit-data
195 ms
hDvwL1_H7g-.css
85 ms
56WNbrUYLbL.css
108 ms
q68gy-v_YMF.js
144 ms
FJmpeSpHpjS.js
170 ms
0wM5s1Khldu.js
141 ms
1bNoFZUdlYZ.js
138 ms
10565175_715857391818726_3879602270056959529_n.jpg
145 ms
429491_283313985073071_285578519_n.jpg
82 ms
969814_10200327251169185_1988420052_n.jpg
109 ms
12107122_10200948798798852_7534634606325598945_n.jpg
88 ms
12019989_1505431459777539_5717571658462257583_n.jpg
87 ms
12208361_953806858029413_794862309769212720_n.jpg
86 ms
625537_10202315479468589_1412732047_n.jpg
166 ms
wL6VQj7Ab77.png
20 ms
s7jcwEQH7Sx.png
21 ms
style_rtl.css
178 ms
mootools.js
654 ms
banner.js
326 ms
sliding-tabs.js
346 ms
I6-MnjEovm5.js
20 ms
pQrUxxo5oQp.js
20 ms
%D7%A6%D7%95%D7%95%D7%AA%20%D7%AA%D7%9E%D7%99%D7%9B%D7%94.jpg
499 ms
%D7%A1%D7%9C%D7%99%D7%A7%D7%94%20%D7%91%D7%A9%D7%A2%D7%94.jpg
499 ms
%D7%9E%D7%A2%D7%A8%D7%9B%D7%AA%20%D7%94%D7%AA%D7%90%D7%9E%D7%95%D7%AA%20%D7%90%D7%A9%D7%A8%D7%90%D7%99.jpg
638 ms
%D7%9E%D7%9E%D7%A9%D7%A7%20%D7%9C%D7%A0%D7%99%D7%94%D7%95%D7%9C%20%D7%AA%D7%9B%D7%A0%D7%95%D7%AA.jpg
1538 ms
arw_rtl.png
304 ms
22 ms
pelecard.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-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
pelecard.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
Browser errors were logged to the console
pelecard.com 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
Tap targets are not sized appropriately
N/A
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pelecard.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is . Our system also found out that Pelecard.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.
pelecard.com
Open Graph description is not detected on the main page of Pelecard. 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: