4.8 sec in total
884 ms
3.5 sec
437 ms
Welcome to wgtowncenter.com homepage info - get ready to check Wg Town Center best content right away, or after learning these important things about wgtowncenter.com
Enjoy your Kissimmee-Orlando vacation with spacious accommodation and a wide-variety of resort amenities for the whole family. Book your stay today!
Visit wgtowncenter.comWe analyzed Wgtowncenter.com page load time and found that the first response time was 884 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wgtowncenter.com performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value19.9 s
0/100
25%
Value15.5 s
0/100
10%
Value7,580 ms
0/100
30%
Value0.013
100/100
15%
Value35.2 s
0/100
10%
884 ms
132 ms
21 ms
27 ms
63 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wgtowncenter.com, 10% (13 requests) were made to Fonts.gstatic.com and 6% (8 requests) were made to Cdn.userway.org. The less responsive or slowest element that took the longest time to load (884 ms) relates to the external source Westgateresorts.com.
Page size can be reduced by 551.8 kB (24%)
2.3 MB
1.7 MB
In fact, the total size of Wgtowncenter.com main page is 2.3 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. Only a small number of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 253.8 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 253.8 kB or 77% of the original size.
Potential reduce by 0 B
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. Wg Town Center images are well optimized though.
Potential reduce by 292.9 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 292.9 kB or 16% of the original size.
Potential reduce by 5.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. Wgtowncenter.com has all CSS files already compressed.
Number of requests can be reduced by 74 (70%)
106
32
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wg Town Center. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
884 ms
gtm.js
132 ms
analytics.min.js
21 ms
postscribe.min.js
27 ms
js
63 ms
analytics.js
161 ms
destination
166 ms
quant.js
282 ms
core.js
156 ms
pixel.js
278 ms
widget.js
296 ms
athelas.css
101 ms
jquery-ui.min.css
125 ms
social-media-tabs.min.css
123 ms
photoswipe.css
126 ms
main.min.css
206 ms
westgate-town-center-resort.min.css
228 ms
fliptoTownCenter.min.js
206 ms
satelliteLib-ef36e9e1f3553fe8466e99fc8fb998f44552049c.js
263 ms
wgr-libs.min.js
261 ms
wgr.min.js
245 ms
api.js
278 ms
sfm.min.js
244 ms
element.js
277 ms
collect
114 ms
collect
136 ms
collect
124 ms
collect
141 ms
css
87 ms
css
108 ms
css
108 ms
config
27 ms
rp.gif
28 ms
t2_37cbtmx8_telemetry
17 ms
ga-audiences
653 ms
ga-audiences
81 ms
js
270 ms
mbox-contents-43310eadd728ec33495363a601a7e0534c4734c9.js
18 ms
player.js
65 ms
json
193 ms
integration-kit-bundle.js
206 ms
getImage
172 ms
285848374
184 ms
getImage
498 ms
getImage
125 ms
getImage
126 ms
getImage
123 ms
getImage
123 ms
getImage
122 ms
getImage
466 ms
1485116623-d1336f7e3720295ad2dbace868c8f42f6aadb0c6c4e22731d21879afa6fc590b-d
343 ms
fbevents.js
343 ms
WJMKSSL
397 ms
widget_async.js
397 ms
7uwwl3m4n7
420 ms
5WeufNNQ2YFgW6okH.png
380 ms
events.js
395 ms
events.js
419 ms
boot.js
393 ms
dtag.js
378 ms
S6uyw4BMUTPHjx4wWw.ttf
403 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
428 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf
502 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58a-xw.ttf
501 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
501 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
501 ms
athelas-bold-webfont.woff
154 ms
ccbc313f-09f8-4017-8d10-054cf972a9ab.js
440 ms
s-code-contents-63fae58de300fdde169c71a9912101369f70263a.js
107 ms
586 ms
widget_app_base_1716562046528.js
238 ms
ytag.min.js
227 ms
recaptcha__en.js
215 ms
boot.js
139 ms
widget_async.js
130 ms
jls86nL8en
547 ms
sa.css
37 ms
clarity.js
86 ms
main.MTBjMzdlM2YyMA.js
85 ms
saq_pxl
75 ms
style-cart.f0a98d04ad37baffcf4a.css
262 ms
fonts.eacdf4961de415ddab83.css
260 ms
triggerRunner.js
66 ms
anchor
42 ms
widget.js
3 ms
styles__ltr.css
5 ms
recaptcha__en.js
17 ms
qnm01WqSoqK7Jyx1yaELvF3K6C5BI8IwwjZQJfkFqNo.js
87 ms
webworker.js
88 ms
logo_48.png
64 ms
output.05e43dd6d2b8.js
127 ms
js
62 ms
djangojs.js
122 ms
output.af4ef1252cd9.js
151 ms
recaptcha__en.js
97 ms
en-US.json
63 ms
satellite-5af344aa64746d7493007623.js
59 ms
params
136 ms
getImage
112 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
93 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
92 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
92 ms
collect
60 ms
04F409CB-703C-4190-BCE1-8500B23381BB
54 ms
collect
21 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
15 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
15 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
15 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
13 ms
params
52 ms
c.gif
229 ms
fd5af758e8594688a85dcf9e26f5579d.js
157 ms
input.js
32 ms
status
158 ms
261600-reviews.js
382 ms
remediation_1716562046528.js
80 ms
491P8xgpv9t6QEXA.json
97 ms
body_wh.svg
54 ms
spin_wh.svg
59 ms
iframe
316 ms
remediation-tool.js
10 ms
jquery-combined.min.js
41 ms
plpixel
94 ms
pl.2.2.min.js
16 ms
wgtowncenter.com accessibility score
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
wgtowncenter.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
Missing source maps for large first-party JavaScript
wgtowncenter.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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wgtowncenter.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 Wgtowncenter.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.
wgtowncenter.com
Open Graph description is not detected on the main page of Wg Town Center. 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: