1.8 sec in total
403 ms
1.2 sec
219 ms
Click here to check amazing Cityof Lafayette content for United States. Otherwise, check out these important facts you probably never knew about cityoflafayette.com
Home
Visit cityoflafayette.comWe analyzed Cityoflafayette.com page load time and found that the first response time was 403 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
cityoflafayette.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value33.7 s
0/100
25%
Value15.6 s
0/100
10%
Value1,660 ms
11/100
30%
Value0.227
55/100
15%
Value19.5 s
2/100
10%
403 ms
144 ms
214 ms
70 ms
188 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 93% of them (67 requests) were addressed to the original Cityoflafayette.com, 3% (2 requests) were made to Code.jquery.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (403 ms) belongs to the original domain Cityoflafayette.com.
Page size can be reduced by 292.1 kB (21%)
1.4 MB
1.1 MB
In fact, the total size of Cityoflafayette.com main page is 1.4 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 58.0 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 58.0 kB or 78% of the original size.
Potential reduce by 90.5 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. Cityof Lafayette images are well optimized though.
Potential reduce by 137.0 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 137.0 kB or 68% of the original size.
Potential reduce by 6.6 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. Cityoflafayette.com needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 51% of the original size.
Number of requests can be reduced by 12 (17%)
70
58
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cityof Lafayette. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
cityoflafayette.com
403 ms
513112995.css
144 ms
-248867905.js
214 ms
1127434005.js
70 ms
-212365995.js
188 ms
WebResource.axd
101 ms
ScriptResource.axd
135 ms
FeatureAreaSearchAutoComplete.css
77 ms
jquery-ui.css
27 ms
jquery.ui.core.min.js
110 ms
jquery.ui.widget.min.js
133 ms
jquery.ui.position.min.js
140 ms
jquery.ui.autocomplete.min.js
144 ms
MouseOverMenu.js
136 ms
-1992112027.js
138 ms
bkg.jpg
47 ms
Path
48 ms
DashboardShot.png
48 ms
baHome.png
47 ms
baPrint.png
45 ms
baTranslate.png
46 ms
bb.jpg
66 ms
Services.jpg
72 ms
Community.jpg
75 ms
Business.jpg
74 ms
Government.jpg
72 ms
go.jpg
76 ms
newsHP2.png
127 ms
viewall.png
125 ms
activitiesHP.png
127 ms
citymeetingsHP.png
130 ms
Invest%20in%20Lafayette%20179%20pix.jpg
129 ms
payonlineHP.png
128 ms
streamingHP.png
171 ms
questionsconcernsHP.png
169 ms
notifymeHP.png
176 ms
jobsHP.png
178 ms
share.png
162 ms
icon-close.gif
163 ms
rss.png
194 ms
email.png
198 ms
facebook.png
199 ms
twitter.png
201 ms
balloon.jpg
211 ms
gallery.jpg
245 ms
logo.png
226 ms
GlobalToolbarBkg.png
229 ms
ButtonRightBkg.png
229 ms
ButtonLeftBkg.png
230 ms
shdbkg.jpg
202 ms
topbkgHP.jpg
255 ms
bc.jpg
225 ms
Services2.jpg
222 ms
Community2.jpg
219 ms
Business2.jpg
231 ms
Government2.jpg
234 ms
tblbkgHP.jpg
261 ms
tbltopHP.jpg
243 ms
tblbtmHP.jpg
244 ms
leftnavbkg.png
242 ms
footer.jpg
244 ms
analytics.js
26 ms
ui-bg_flat_75_ffffff_40x100.png
10 ms
Boy%20and%20Moon.jpg
272 ms
Fest%20Plaza.jpg
348 ms
collect
12 ms
golfcourse.jpg
239 ms
InvestLaf252x210.jpg
312 ms
Library2_IMG_9170_252x210.jpg
309 ms
PeachFest.jpg
253 ms
Solar.jpg
274 ms
piwik.js
129 ms
cityoflafayette.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
cityoflafayette.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
Page has valid source maps
cityoflafayette.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Cityoflafayette.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 Cityoflafayette.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.
cityoflafayette.com
Open Graph description is not detected on the main page of Cityof Lafayette. 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: