1.9 sec in total
184 ms
1.6 sec
69 ms
Visit greenbyphone.com now to see the best up-to-date Green Byphone content for United States and also check out these interesting facts you probably never knew about greenbyphone.com
The oldest, most well respected e-check processor in the United States.
Visit greenbyphone.comWe analyzed Greenbyphone.com page load time and found that the first response time was 184 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
greenbyphone.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.1 s
3/100
25%
Value6.7 s
37/100
10%
Value2,240 ms
6/100
30%
Value0.002
100/100
15%
Value13.3 s
12/100
10%
184 ms
222 ms
135 ms
134 ms
29 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Greenbyphone.com, 92% (150 requests) were made to Static.parastorage.com and 4% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 1.7 MB (29%)
5.9 MB
4.2 MB
In fact, the total size of Greenbyphone.com main page is 5.9 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. 85% 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.6 MB which makes up the majority of the site volume.
Potential reduce by 66.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. 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 66.3 kB or 78% of the original size.
Potential reduce by 61.6 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. Green Byphone images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 65% of the original size.
Potential reduce by 513.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. Greenbyphone.com needs all CSS files to be minified and compressed as it can save up to 513.8 kB or 84% of the original size.
Number of requests can be reduced by 153 (96%)
159
6
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Green Byphone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 149 to 1 for JavaScripts and as a result speed up the page load time.
greenbyphone.com
184 ms
greenbyphone.com
222 ms
green.money
135 ms
www.green.money
134 ms
require.min.js
29 ms
main-r.min.js
29 ms
bt
15 ms
ugc-viewer
10 ms
467a3a_177b0e1b60a57125d74b9acbac0858b7_3808.json.z
67 ms
467a3a_432e90d63e510f6ab51d68d97148aaf4_3802.json.z
478 ms
bt
19 ms
react-with-addons.min.js
27 ms
lodash.min.js
15 ms
wixCodeInit.min.js
27 ms
coreUtils.js
61 ms
coreUtils.min.js
37 ms
skins.min.js
129 ms
components.min.js
54 ms
core.min.js
63 ms
mobx.umd.min.js
60 ms
mobx-react.min.js
62 ms
TweenMax.min.js
128 ms
animations.min.js
128 ms
react-with-addons.min.js
130 ms
layout.min.js
135 ms
wixappsCore.min.js
130 ms
wixappsClassics.min.js
136 ms
container.min.js
133 ms
imageZoom.min.js
133 ms
mediaZoom.min.js
136 ms
imageZoomDisplayer.min.js
135 ms
matrixGallery.min.js
137 ms
slideShowGallery.min.js
140 ms
comboBoxInput.min.js
138 ms
dialogs.min.js
140 ms
table.min.js
142 ms
wixappsBuilder.min.js
143 ms
tpa.min.js
142 ms
dataFixer.min.js
144 ms
siteUtils.min.js
144 ms
image.min.js
145 ms
balata.min.js
147 ms
translationsUtils.min.js
148 ms
hammer.min.js
153 ms
utils.min.js
153 ms
fonts.min.js
148 ms
platformUtils-bundle.js
151 ms
loggingUtils.min.js
149 ms
imageClientApi.js
137 ms
swfobject.min.js
129 ms
santaProps.min.js
125 ms
displayer.min.js
108 ms
mousetrap.min.js
107 ms
DrawSVGPlugin.min.js
106 ms
react-dom.min.js
105 ms
ScrollToPlugin.min.js
101 ms
widgets.min.js
334 ms
react-dom-server.min.js
334 ms
imageCommon.min.js
335 ms
formCommon.min.js
335 ms
textCommon.min.js
333 ms
containerCommon.min.js
333 ms
socialCommon.min.js
333 ms
galleriesCommon.min.js
332 ms
buttonCommon.min.js
332 ms
compDesignUtils.min.js
331 ms
mediaCommon.min.js
331 ms
audioCommon.min.js
331 ms
skinExports.min.js
330 ms
compUtils.min.js
330 ms
mobileLayoutUtils.js
329 ms
pm-rpc.min.js
328 ms
tweenEngine.min.js
329 ms
multilingual.min.js
328 ms
render.min.js
327 ms
color.min.js
326 ms
zepto.min.js
326 ms
xss.min.js
325 ms
bluebird.min.js
325 ms
imageClientApi.min.js
322 ms
column.min.js
321 ms
siteBackground.min.js
322 ms
hoverBox.min.js
322 ms
mediaContainerFactory.min.js
321 ms
internalMarkings.min.js
321 ms
repeater.min.js
318 ms
zoomedImage.min.js
318 ms
menuButton.min.js
318 ms
messageView.min.js
107 ms
backgroundCommon.min.js
79 ms
bt
101 ms
css
39 ms
TweenMax.min.js
29 ms
svgShape.min.js
17 ms
adminLoginButton.min.js
17 ms
wTwitterFollow.min.js
18 ms
facebookComments.min.js
19 ms
verticalAnchorsMenu.min.js
22 ms
facebookShare.min.js
20 ms
vKShareButton.min.js
22 ms
youTubeSubscribeButton.min.js
23 ms
itunesButton.min.js
22 ms
skypeCallButton.min.js
25 ms
fileUploader.min.js
24 ms
pinItPinWidget.min.js
26 ms
popupCloseTextButton.min.js
25 ms
radioButton.min.js
25 ms
radioGroup.min.js
26 ms
documentMedia.min.js
26 ms
datePicker.min.js
27 ms
contactForm.min.js
28 ms
subscribeForm.min.js
27 ms
textArea.min.js
29 ms
loginSocialBar.min.js
29 ms
googleMap.min.js
30 ms
soundCloudWidget.min.js
31 ms
paypalButton.min.js
32 ms
imageButton.min.js
33 ms
linkBar.min.js
34 ms
spotifyPlayer.min.js
35 ms
spotifyFollow.min.js
36 ms
twitterFeed.min.js
38 ms
backToTopButton.min.js
35 ms
svgCommon.min.js
36 ms
facebookLike.min.js
38 ms
facebookLikeBox.min.js
37 ms
flickrBadgeWidget.min.js
38 ms
rssButton.min.js
68 ms
tinyMenu.min.js
63 ms
groupContainer.min.js
63 ms
wGooglePlusOne.min.js
62 ms
pinterestPinIt.min.js
62 ms
pinterestFollow.min.js
62 ms
wTwitterTweet.min.js
62 ms
audioPlayer.min.js
61 ms
loginButton.min.js
61 ms
htmlComponent.min.js
61 ms
deadComponent.min.js
61 ms
mediaPlayer.min.js
61 ms
mediaControls.min.js
60 ms
singleAudioPlayer.min.js
60 ms
quickActionBar.min.js
62 ms
boxSlideShowSlide.min.js
60 ms
stripSlideShowSlide.min.js
59 ms
page.min.js
60 ms
bgImageStrip.min.js
58 ms
popupContainer.min.js
60 ms
stripContainer.min.js
60 ms
stripColumnsContainer.min.js
58 ms
exitMobileModeButton.min.js
58 ms
tpaGalleries.min.js
58 ms
flashComponent.min.js
58 ms
stripSlideShow.min.js
57 ms
mobileActionsMenu.min.js
57 ms
verticalMenu.min.js
56 ms
disqusComments.min.js
57 ms
checkbox.min.js
55 ms
gridComponent.min.js
57 ms
languageSelector.min.js
57 ms
lodash.min.js
10 ms
bt
5 ms
languages.css
61 ms
bt
7 ms
greenbyphone.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
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
greenbyphone.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
greenbyphone.com SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenbyphone.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Greenbyphone.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.
greenbyphone.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: