63.6 sec in total
275 ms
51.4 sec
12 sec
Click here to check amazing City Of Lewisville content for United States. Otherwise, check out these important facts you probably never knew about cityoflewisville.com
Lewisville, TX, is a dynamic suburban community in the thriving North Texas region. Home to approximately 132,620 residents.
Visit cityoflewisville.comWe analyzed Cityoflewisville.com page load time and found that the first response time was 275 ms and then it took 63.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
cityoflewisville.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.3 s
0/100
25%
Value7.3 s
29/100
10%
Value380 ms
70/100
30%
Value0
100/100
15%
Value11.4 s
19/100
10%
275 ms
1766 ms
563 ms
1787 ms
3425 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 76% of them (80 requests) were addressed to the original Cityoflewisville.com, 9% (9 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (13.7 sec) relates to the external source Googletagmanager.com.
Page size can be reduced by 674.4 kB (10%)
6.5 MB
5.8 MB
In fact, the total size of Cityoflewisville.com main page is 6.5 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 5.7 MB which makes up the majority of the site volume.
Potential reduce by 73.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 73.3 kB or 78% of the original size.
Potential reduce by 130.2 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. City Of Lewisville images are well optimized though.
Potential reduce by 291.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 291.7 kB or 58% of the original size.
Potential reduce by 179.1 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. Cityoflewisville.com needs all CSS files to be minified and compressed as it can save up to 179.1 kB or 82% of the original size.
Number of requests can be reduced by 37 (39%)
94
57
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Of Lewisville. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
cityoflewisville.com
275 ms
www.cityoflewisville.com
1766 ms
bootstrap.min.css
563 ms
StyleBundleDesignTheme.cssbnd
1787 ms
StyleBundleDesignTheme.cssbnd
3425 ms
StyleBundleFrontendExtra.cssbnd
4186 ms
StyleBundleKendo.cssbnd
2444 ms
ScriptBundleFAllInOne.jsbnd
3409 ms
x-small.css
4132 ms
StyleBundleAngularLib.cssbnd
4222 ms
ScriptBundleAngularLib.jsbnd
4274 ms
element.js
63 ms
StyleBundleMegaMenuDropDown.cssbnd
4194 ms
StyleBundleMegaMenuDropDown.cssbnd
4194 ms
jquery.fancybox.js
4158 ms
jquery.fancybox-media.js
4208 ms
jquery.fancybox.css
4168 ms
homelayout_scripts.js
4169 ms
mobile_nav_scripts.js
4168 ms
slick.min.js
4169 ms
ScriptBundleVisionFrontend.jsbnd
4169 ms
ScriptBundleKendo.jsbnd
4244 ms
ScriptsFEBundle.jsbnd
3816 ms
css
1047 ms
css
981 ms
css
980 ms
Print.cssbnd
3168 ms
analytics.js
592 ms
spacer.gif
1814 ms
ShowImage
1796 ms
ShowImage
1796 ms
ShowImage
1920 ms
ShowImage
1909 ms
ShowImage
1909 ms
ShowImage
1908 ms
ShowImage
1909 ms
ShowImage
1905 ms
ShowImage
1874 ms
ShowImage
1875 ms
ShowImage
1874 ms
ShowImage
1933 ms
ShowImage
1928 ms
ShowImage
1913 ms
ShowImage
1890 ms
ShowImage
1891 ms
ShowImage
1891 ms
ShowImage
1858 ms
ShowImage
1857 ms
ShowImage
1925 ms
ShowImage
1925 ms
ShowImage
1965 ms
ShowImage
1965 ms
ShowImage
1966 ms
ShowImage
1966 ms
ShowImage
1967 ms
ShowImage
1966 ms
ShowImage
1919 ms
linkid.js
178 ms
Print.cssbnd
362 ms
messagebox_strip.gif
506 ms
header_bg.png
398 ms
logo.png
398 ms
menu.png
397 ms
ShowImage
380 ms
arrow_translate.png
379 ms
collect
67 ms
collect
957 ms
translateelement.css
649 ms
main.js
1691 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
1754 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
1754 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
2255 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
2402 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
2403 ms
search_input_bg.png
1021 ms
color_border.png
733 ms
0XxGQsSc1g4rdRdjJKZrNMDdSZkkecOE1hvV7ZHvhyU.ttf
721 ms
G0XvmuebhPCfCq4YdUpRgALUuEpTyoUstqEm5AMlJo4.ttf
1078 ms
ShowImage
590 ms
element_main.js
230 ms
zhcz-_WihjSQC0oHJ9TCYMDdSZkkecOE1hvV7ZHvhyU.ttf
229 ms
IQHow_FEYlDC4Gzy_m8fcsBaWKZ57bY3RXgXH6dOjZ0.ttf
531 ms
graphic_bg.jpg
620 ms
btn_violet.jpg
754 ms
btn_green.jpg
756 ms
btn_orange.jpg
566 ms
arrow_left.png
754 ms
arrow_right.png
753 ms
accent_small.jpg
516 ms
accent_big.jpg
320 ms
footer_bg.png
323 ms
fullsite_bg.gif
584 ms
fullsite_arrow_left.png
584 ms
gtm.js
13743 ms
ShowImage
6468 ms
ShowImage
1506 ms
ShowImage
1849 ms
ShowImage
1462 ms
ShowImage
1028 ms
ShowImage
1459 ms
button_arrows.png
1027 ms
translate_24dp.png
1355 ms
l
950 ms
googlelogo_color_42x16dp.png
823 ms
translate_24dp.png
204 ms
cityoflewisville.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.
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
cityoflewisville.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cityoflewisville.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cityoflewisville.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 Cityoflewisville.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.
cityoflewisville.com
Open Graph description is not detected on the main page of City Of Lewisville. 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: