1.1 sec in total
81 ms
993 ms
71 ms
Click here to check amazing My Grace Space content. Otherwise, check out these important facts you probably never knew about mygracespace.com
Welcome to Grace Fellowship Church of North Augusta's website. We hope you find it helpful and informative. See the Service times so you can come and join us.
Visit mygracespace.comWe analyzed Mygracespace.com page load time and found that the first response time was 81 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
mygracespace.com performance score
name
value
score
weighting
Value3.6 s
33/100
10%
Value9.9 s
0/100
25%
Value14.2 s
1/100
10%
Value21,530 ms
0/100
30%
Value0.183
66/100
15%
Value31.8 s
0/100
10%
81 ms
110 ms
60 ms
20 ms
22 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Mygracespace.com, 93% (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 (204 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 677.0 kB (62%)
1.1 MB
417.5 kB
In fact, the total size of Mygracespace.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. 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. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 60.9 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 60.9 kB or 81% of the original size.
Potential reduce by 615.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 615.6 kB or 61% of the original size.
Potential reduce by 557 B
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. Mygracespace.com has all CSS files already compressed.
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 My Grace Space. 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.
mygracespace.com
81 ms
www.mygracespace.com
110 ms
www.gfcna.net
60 ms
require.min.js
20 ms
main-r.min.js
22 ms
bt
34 ms
784099_55b1f3b1d1bec8f286bf5021b60bdc5a_188.json.z
201 ms
784099_cbd425ee9ca3d86b84a77e9fd015a6e5_186.json.z
204 ms
ugc-viewer
30 ms
bt
55 ms
react-with-addons.min.js
17 ms
lodash.min.js
12 ms
wixCodeInit.min.js
34 ms
coreUtils.js
29 ms
coreUtils.min.js
33 ms
skins.min.js
53 ms
components.min.js
49 ms
core.min.js
52 ms
mobx.umd.min.js
53 ms
mobx-react.min.js
51 ms
TweenMax.min.js
50 ms
animations.min.js
53 ms
react-with-addons.min.js
169 ms
layout.min.js
168 ms
wixappsCore.min.js
169 ms
wixappsClassics.min.js
53 ms
container.min.js
51 ms
imageZoom.min.js
170 ms
mediaZoom.min.js
169 ms
imageZoomDisplayer.min.js
170 ms
matrixGallery.min.js
170 ms
slideShowGallery.min.js
170 ms
comboBoxInput.min.js
167 ms
dialogs.min.js
171 ms
table.min.js
171 ms
wixappsBuilder.min.js
171 ms
tpa.min.js
173 ms
dataFixer.min.js
171 ms
siteUtils.min.js
172 ms
image.min.js
172 ms
balata.min.js
176 ms
translationsUtils.min.js
173 ms
hammer.min.js
174 ms
utils.min.js
175 ms
fonts.min.js
174 ms
platformUtils-bundle.js
171 ms
loggingUtils.min.js
171 ms
imageClientApi.js
173 ms
swfobject.min.js
153 ms
santaProps.min.js
153 ms
displayer.min.js
143 ms
mousetrap.min.js
134 ms
DrawSVGPlugin.min.js
134 ms
react-dom.min.js
134 ms
ScrollToPlugin.min.js
135 ms
widgets.min.js
135 ms
react-dom-server.min.js
134 ms
imageCommon.min.js
134 ms
formCommon.min.js
133 ms
textCommon.min.js
130 ms
containerCommon.min.js
136 ms
socialCommon.min.js
136 ms
galleriesCommon.min.js
136 ms
buttonCommon.min.js
136 ms
compDesignUtils.min.js
135 ms
mediaCommon.min.js
136 ms
audioCommon.min.js
135 ms
skinExports.min.js
135 ms
compUtils.min.js
135 ms
mobileLayoutUtils.js
135 ms
pm-rpc.min.js
135 ms
tweenEngine.min.js
135 ms
multilingual.min.js
133 ms
render.min.js
134 ms
color.min.js
133 ms
zepto.min.js
134 ms
xss.min.js
133 ms
bluebird.min.js
133 ms
imageClientApi.min.js
133 ms
column.min.js
132 ms
siteBackground.min.js
133 ms
hoverBox.min.js
132 ms
mediaContainerFactory.min.js
131 ms
internalMarkings.min.js
132 ms
repeater.min.js
131 ms
zoomedImage.min.js
132 ms
menuButton.min.js
132 ms
messageView.min.js
132 ms
backgroundCommon.min.js
35 ms
bt
105 ms
css
77 ms
TweenMax.min.js
24 ms
svgShape.min.js
13 ms
adminLoginButton.min.js
12 ms
wTwitterFollow.min.js
12 ms
facebookComments.min.js
13 ms
verticalAnchorsMenu.min.js
13 ms
facebookShare.min.js
13 ms
vKShareButton.min.js
14 ms
youTubeSubscribeButton.min.js
15 ms
itunesButton.min.js
14 ms
skypeCallButton.min.js
15 ms
fileUploader.min.js
16 ms
pinItPinWidget.min.js
15 ms
popupCloseTextButton.min.js
15 ms
radioButton.min.js
16 ms
radioGroup.min.js
16 ms
documentMedia.min.js
16 ms
datePicker.min.js
29 ms
contactForm.min.js
28 ms
subscribeForm.min.js
28 ms
textArea.min.js
29 ms
loginSocialBar.min.js
28 ms
googleMap.min.js
28 ms
soundCloudWidget.min.js
31 ms
paypalButton.min.js
28 ms
imageButton.min.js
29 ms
linkBar.min.js
32 ms
spotifyPlayer.min.js
31 ms
spotifyFollow.min.js
29 ms
twitterFeed.min.js
31 ms
backToTopButton.min.js
32 ms
svgCommon.min.js
33 ms
facebookLike.min.js
33 ms
facebookLikeBox.min.js
32 ms
flickrBadgeWidget.min.js
33 ms
rssButton.min.js
33 ms
tinyMenu.min.js
29 ms
groupContainer.min.js
29 ms
wGooglePlusOne.min.js
30 ms
pinterestPinIt.min.js
29 ms
pinterestFollow.min.js
29 ms
wTwitterTweet.min.js
28 ms
audioPlayer.min.js
29 ms
loginButton.min.js
28 ms
htmlComponent.min.js
28 ms
deadComponent.min.js
28 ms
mediaPlayer.min.js
28 ms
mediaControls.min.js
41 ms
singleAudioPlayer.min.js
42 ms
quickActionBar.min.js
41 ms
boxSlideShowSlide.min.js
41 ms
stripSlideShowSlide.min.js
40 ms
page.min.js
31 ms
bgImageStrip.min.js
28 ms
popupContainer.min.js
29 ms
stripContainer.min.js
29 ms
stripColumnsContainer.min.js
29 ms
exitMobileModeButton.min.js
29 ms
tpaGalleries.min.js
30 ms
flashComponent.min.js
29 ms
stripSlideShow.min.js
29 ms
mobileActionsMenu.min.js
29 ms
verticalMenu.min.js
29 ms
disqusComments.min.js
28 ms
checkbox.min.js
28 ms
gridComponent.min.js
28 ms
languageSelector.min.js
28 ms
lodash.min.js
3 ms
languages.css
27 ms
bt
52 ms
bt
8 ms
mygracespace.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mygracespace.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
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 Mygracespace.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 Mygracespace.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.
mygracespace.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: