Lafayettela.Gov - Info lafayettela.gov

lafayettela.gov receives about 1,697 unique visitors and 6,448 (3.80 per visitor) page views per day which should earn about $73.95/day from advertising revenue. Estimated site value is $53,990.70. According to Alexa Traffic Rank lafayettela.gov is ranked number 439,050 in the world and 0.0001% of global Internet users visit it. Site is hosted in Lafayette, Louisiana, 70506, United States and links to network IP address 12.166.209.100. This server supports HTTPS and doesn't support HTTP/2.

About - lafayettela.gov


Technologies used on Website

Web Servers
IIS
Web Frameworks
Microsoft ASP.NET
CMS
Microsoft SharePoint
Operating Systems
Windows Server

lafayettela.gov Profile

Last update was 120 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with lafayettela.gov in any way. Only publicly available statistics data are displayed.

How popular is lafayettela.gov?

1.7K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,697
Monthly Unique Visitors:
40,728
Pages per Visit:
3.80
Daily Pageviews:
6,448
Alexa Rank:
439,050 visit alexa
Alexa Reach:
0.0001%   (of global internet users)
Avg. visit duration:
07:59
Bounce rate:
67.30%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
38.32%
Referral:
50.28%
Search:
11.39%
Social:
0%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
United States 100.0%100.0%66699

Where do visitors go on this site?

Reach%Pageviews%PerUser
lafayettela.gov
92.89%97.81%6.2
OTHER
0%2.16%0

Competitive Data

SEMrush
Domain:
  lafayettela.gov
Rank:
(Rank based on keywords, cost and organic traffic)
  75,940
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  9,001
Organic Traffic:
(Number of visitors coming from top 20 search results)
  23,017
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $26,126.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is lafayettela.gov?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
lafayettela.gov
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
lafayettela.gov
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much lafayettela.gov can earn?

Daily Revenue:
$73.95
Monthly Revenue:
$2,218.50
Yearly Revenue:
$26,991.75
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 6,448$73.96

How much money do lafayettela.gov lose due to Adblock?

Daily Revenue Loss:
$13.31
Monthly Revenue Loss:
$399.38
Yearly Revenue Loss:
$4,859.08
Daily Pageviews Blocked:
1,161
Monthly Pageviews Blocked:
34,819
Yearly Pageviews Blocked:
423,634
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 1,161$13.31

How much is lafayettela.gov worth?

Website Value:
$53,990.70

+ Where is lafayettela.gov hosted?

Server IP:
12.166.209.100
ASN:
AS25921 
ISP:
Lafayette Consolidated Government 
Server Location:
Lafayette
Louisiana, LA
70506
United States, US
 

Other sites hosted on 12.166.209.100

+ How fast does lafayettela.gov load?

Average Load Time:
(617 ms) 88 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.0s 46% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 46% 48% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 48% 4% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 4%
First Input Delay (FID)5ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)2.0s 46% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 46% 48% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 48% 4% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 4%
First Input Delay (FID)5ms 99% of loads for this page have a fast (<50ms) First Input Delay (FID) 99% 0% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>250ms) First Input Delay (FID) 0%

Lab Data

Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
88 ms4 ms1 ms
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
69 ms31 ms6 ms
Remove unused CSS - Potential savings of 35 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB35 KB
Avoids enormous network payloads - Total size was 506 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
288 KB
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB
http://lafayettela.gov/Pages/Index.aspx
15 KB
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
10 KB
http://lafayettela.gov/SiteAssets/Images/media-image.png
5 KB
http://lafayettela.gov/SiteAssets/Images/calendar.png
5 KB
http://lafayettela.gov/SiteAssets/Images/pay-online.png
5 KB
http://lafayettela.gov/SiteAssets/Images/services.png
5 KB
http://lafayettela.gov/SiteAssets/Images/media-center.png
5 KB
Minimizes main-thread work - 0.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
41 ms
Script Evaluation
39 ms
Other
36 ms
Rendering
20 ms
Parse HTML & CSS
19 ms
Script Parsing & Compilation
9 ms
Serve images in next-gen formats - Potential savings of 258 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
287 KB258 KB
Avoids an excessive DOM size - 523 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
523
Maximum DOM Depth
19
Maximum Child Elements
16
Minify JavaScript - Potential savings of 48 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB45 KB
inline: var imgs; var imgIdx = 0; v...
4 KB2 KB
Avoid multiple page redirects - Potential savings of 190 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://lafayettela.gov/)
0
http://lafayettela.gov/Pages/Index.aspx
190
Keep request counts low and transfer sizes small - 24 requests • 506 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
24506 KB
Image
15345 KB
Script
4101 KB
Stylesheet
345 KB
Document
115 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 330 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB310
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
10 KB150
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://lafayettela.gov/
0 ms60 ms0 KB0 KB302text/html
http://lafayettela.gov/Pages/Index.aspx
60 ms1009 ms15 KB48 KB200text/htmlDocument
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
1021 ms1155 ms100 KB254 KB200application/x-javascriptScript
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
1022 ms1080 ms10 KB35 KB200text/cssStylesheet
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
1022 ms1110 ms35 KB145 KB200text/cssStylesheet
http://lafayettela.gov/SiteAssets/CSS/lcg_master.css
1022 ms1026 ms0 KB0 KB-1Stylesheet
http://lafayettela.gov/_layouts/1033/init.js?rev=0OHTJmtljdkrRniX3Vao7A%3D%3D
1022 ms1026 ms0 KB0 KB-1Script
http://lafayettela.gov/WebResource.axd?d=hsyXZEerXwXvTX_bRiygEP9LguSc6Dlvuby3qkk3MwlnBy2MjuZ4xhyl9nBbxWJjvYiJVNLDgzJBUKqQz0X21p58z--HFD1yx6-4Jty_TMVqQ-AtJAC4nCbDX9S7wjcx3Qg7SN7shDv4akj22b9imTzya-Y1&t=636767426854137053
1022 ms1026 ms0 KB0 KB-1Script
http://lafayettela.gov/SiteAssets/Images/lcg-logo.png
1023 ms1026 ms0 KB0 KB-1Image
http://lafayettela.gov/SiteAssets/Images/pay-online.png
1023 ms1075 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/services.png
1076 ms1134 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/calendar.png
1097 ms1155 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/media-center.png
1135 ms1193 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/departments.png
1157 ms1219 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/info.png
1195 ms1259 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/search-icon.png
1195 ms1260 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/_layouts/images/gosearch15.png
1195 ms1247 ms1 KB1 KB200image/pngImage
http://lafayettela.gov/siteassets/js/touch-fix.js
1026 ms1096 ms2 KB2 KB200application/x-javascriptScript
http://lafayettela.gov/SiteAssets/Images/media-image.png
1195 ms1265 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Facebook-Icon.png
1195 ms1258 ms4 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Twitter-Icon.png
1196 ms1259 ms4 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Instagram_Icon.png
1196 ms1247 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/bgximg-9DDB36E5.png?ctag
1218 ms1277 ms3 KB2 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
1263 ms1335 ms288 KB287 KB200image/pngImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1033 ms
7 ms
1042 ms
5 ms
1188 ms
31 ms
1232 ms
54 ms
1286 ms
15 ms
1309 ms
8 ms
1368 ms
5 ms
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Avoid chaining critical requests - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 950 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

88
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 3.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 3.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 3.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 5692.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Remove unused CSS - Potential savings of 35 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB35 KB
Avoids enormous network payloads - Total size was 591 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
288 KB
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB
http://lafayettela.gov/_layouts/1033/init.js?rev=0OHTJmtljdkrRniX3Vao7A%3D%3D
31 KB
http://lafayettela.gov/WebResource.axd?d=hsyXZEerXwXvTX_bRiygEP9LguSc6Dlvuby3qkk3MwlnBy2MjuZ4xhyl9nBbxWJjvYiJVNLDgzJBUKqQz0X21p58z--HFD1yx6-4Jty_TMVqQ-AtJAC4nCbDX9S7wjcx3Qg7SN7shDv4akj22b9imTzya-Y1&t=636767426854137053
30 KB
http://lafayettela.gov/SiteAssets/Images/lcg-logo.png
29 KB
http://lafayettela.gov/Pages/Index.aspx
15 KB
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
10 KB
http://lafayettela.gov/SiteAssets/Images/media-image.png
5 KB
http://lafayettela.gov/SiteAssets/Images/pay-online.png
5 KB
Minimizes main-thread work - 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
291 ms
Script Evaluation
287 ms
Other
244 ms
Rendering
121 ms
Parse HTML & CSS
119 ms
Script Parsing & Compilation
69 ms
Serve images in next-gen formats - Potential savings of 258 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
287 KB258 KB
Avoids an excessive DOM size - 523 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
523
Maximum DOM Depth
19
Maximum Child Elements
16
Minify JavaScript - Potential savings of 48 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB45 KB
inline: var imgs; var imgIdx = 0; v...
4 KB2 KB
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

URL
Time Spent
(Initial: http://lafayettela.gov/)
0
http://lafayettela.gov/Pages/Index.aspx
630
Keep request counts low and transfer sizes small - 24 requests • 591 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
24591 KB
Image
15368 KB
Script
4162 KB
Stylesheet
345 KB
Document
115 KB
Other
10 KB
Media
00 KB
Font
00 KB
Third-party
00 KB
Eliminate render-blocking resources - Potential savings of 1,290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
100 KB1680
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
10 KB630
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
35 KB1230
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://lafayettela.gov/
0 ms63 ms0 KB0 KB302text/html
http://lafayettela.gov/Pages/Index.aspx
64 ms1030 ms15 KB48 KB200text/htmlDocument
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
1052 ms1154 ms100 KB254 KB200application/x-javascriptScript
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
1053 ms1112 ms10 KB35 KB200text/cssStylesheet
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
1053 ms1182 ms35 KB145 KB200text/cssStylesheet
http://lafayettela.gov/SiteAssets/CSS/lcg_master.css
1053 ms1061 ms0 KB0 KB-1Stylesheet
http://lafayettela.gov/_layouts/1033/init.js?rev=0OHTJmtljdkrRniX3Vao7A%3D%3D
1054 ms1256 ms31 KB115 KB200application/x-javascriptScript
http://lafayettela.gov/WebResource.axd?d=hsyXZEerXwXvTX_bRiygEP9LguSc6Dlvuby3qkk3MwlnBy2MjuZ4xhyl9nBbxWJjvYiJVNLDgzJBUKqQz0X21p58z--HFD1yx6-4Jty_TMVqQ-AtJAC4nCbDX9S7wjcx3Qg7SN7shDv4akj22b9imTzya-Y1&t=636767426854137053
1055 ms1224 ms30 KB94 KB200application/x-javascriptScript
http://lafayettela.gov/SiteAssets/Images/lcg-logo.png
1056 ms1188 ms29 KB28 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/pay-online.png
1057 ms1120 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/services.png
1214 ms1278 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/calendar.png
1057 ms1225 ms0 KB0 KB-1Image
http://lafayettela.gov/SiteAssets/Images/media-center.png
1214 ms1287 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/departments.png
1215 ms1276 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/info.png
1215 ms1270 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/search-icon.png
1215 ms1373 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/_layouts/images/gosearch15.png
1215 ms1264 ms1 KB1 KB200image/pngImage
http://lafayettela.gov/siteassets/js/touch-fix.js
1123 ms1249 ms2 KB2 KB200application/x-javascriptScript
http://lafayettela.gov/SiteAssets/Images/media-image.png
1215 ms1279 ms5 KB5 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Facebook-Icon.png
1216 ms1279 ms4 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Twitter-Icon.png
1216 ms1278 ms4 KB4 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/Instagram_Icon.png
1216 ms1269 ms5 KB4 KB200image/pngImage
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/bgximg-9DDB36E5.png?ctag
1296 ms1355 ms3 KB2 KB200image/pngImage
http://lafayettela.gov/SiteAssets/Images/HomepageSlides/311_Homepage_2-01-01.png
1404 ms1514 ms288 KB287 KB200image/pngImage
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
1079 ms
12 ms
1097 ms
10 ms
1212 ms
50 ms
1264 ms
7 ms
1273 ms
7 ms
1309 ms
7 ms
1322 ms
14 ms
1339 ms
28 ms
1370 ms
5 ms
1378 ms
14 ms
1396 ms
20 ms
1416 ms
34 ms
1452 ms
12 ms
1564 ms
8 ms
JavaScript execution time - 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
747 ms24 ms6 ms
http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
296 ms214 ms23 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Avoid chaining critical requests - 7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 970 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

ECONOMIC DEVELOPMENT and 8 others render only 5 pixels tall (13 CSS pixels) .
| and 7 others render only 5 pixels tall (13 CSS pixels) .
Media Center and 5 others render only 4 pixels tall (11 CSS pixels) .
INFRASTRUCTURE and 6 others render only 5 pixels tall (13 CSS pixels) .
| and 5 others render only 5 pixels tall (13 CSS pixels) .
Non-Emergency…our Fingertips renders only 6 pixels tall (16 CSS pixels) .
311 Lafayette Portal​​ and 3 others render only 5 pixels tall (13 CSS pixels) .
​Animal Shelte…tions for Dogs and 4 others render only 5 pixels tall (13 CSS pixels) .
10/24/2019 and 4 others render only 5 pixels tall (13 CSS pixels) .
NOV 11 and 6 others render only 5 pixels tall (13 CSS pixels) .
MON and 6 others render only 5 pixels tall (13 CSS pixels) .
View LIVE City…ty Programming and 7 others render only 5 pixels tall (13 CSS pixels) .
New City Map &amp; New Parish Map and 21 others render only 5 pixels tall (13 CSS pixels) .
QUICK LINKS renders only 4 pixels tall (11 CSS pixels) .
CITY/PARISH SERVICES and 2 others render only 4 pixels tall (11 CSS pixels) .
Disadvantaged…ears 2020-2022 and 31 others render only 5 pixels tall (13 CSS pixels) .
more... and 1 others render only 5 pixels tall (13 CSS pixels) .
Comprehensive Plan and 3 others render only 5 pixels tall (13 CSS pixels) .
Social Media Center renders only 5 pixels tall (13 CSS pixels) .
PUBLIC RECORDS REQUEST and 6 others render only 5 pixels tall (13 CSS pixels) .
| and 5 others render only 5 pixels tall (13 CSS pixels) .

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js
http://lafayettela.gov/_layouts/1033/init.js?rev=0OHTJmtljdkrRniX3Vao7A%3D%3D
http://lafayettela.gov/WebResource.axd?d=hsyXZEerXwXvTX_bRiygEP9LguSc6Dlvuby3qkk3MwlnBy2MjuZ4xhyl9nBbxWJjvYiJVNLDgzJBUKqQz0X21p58z--HFD1yx6-4Jty_TMVqQ-AtJAC4nCbDX9S7wjcx3Qg7SN7shDv4akj22b9imTzya-Y1&t=636767426854137053
http://lafayettela.gov/siteassets/js/touch-fix.js
Optimize CSS Delivery of the following:

http://lafayettela.gov/_catalogs/theme/Themed/9262B884/search-7E1AFF02.css?ctag=2
http://lafayettela.gov/_catalogs/theme/Themed/9262B884/corev4-8A0ABD2F.css?ctag=2
http://lafayettela.gov/SiteAssets/CSS/lcg_master.css

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.aca…orthearts.org/">AcA</a> is close to 2 other tap targets .
The tap target <a href="/Pages/Pay-Online.aspx">Pay Online</a> and 5 others are close to other tap targets .
The tap target <input id="isSearchBox_S3…_InputKeywords" type="text" name="InputKeywords" class="ms-sbplain s4-…ox-QueryPrompt"> is close to 1 other tap targets .
The tap target <a id="isSearchBox_S36190A05_go" href="javascript:S36190A05_Submit()"></a> is close to 1 other tap targets.
The tap target <a href="/pages/latest-news.aspx">LATEST NEWS</a> is close to 1 other tap targets .
The tap target <a href="http://www.laf…e.aspx?id=1126">Revised-Girard…Girard Park Dr</a> and 7 others are close to other tap targets .
The tap target <a href="http://lafayet…s/default.aspx">LCNW Executive…mittee Meeting</a> and 7 others are close to other tap targets .
The tap target <a href="http://www.ust…ouncil-meeting" class="cs-iLink">Council Meeting Archive</a> and 25 others are close to other tap targets .
The tap target <a href="http://www.laf…s/default.aspx" class="mp-iLink">Animal Shelter &amp; Care Center</a> and 32 others are close to other tap targets .
The tap target <a href="http://lafayet…ss-Center.aspx" class="bc-mLink">more...</a> and 1 others are close to other tap targets .
The tap target <a href="http://lafayet…ia-Center.aspx" class="fb3-mmLink">Social Media Center</a> is close to 1 other tap targets .
The tap target <a href="http://lafayet…acypolicy.aspx">PRIVACY POLICY</a> is close to 1 other tap targets .

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,120 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="http://www.lafayette.org/">ECONOMIC DEVELOPMENT</a> falls outside the viewport.
The element <a href="/Pages/Departments.aspx">Departments</a> falls outside the viewport.
The element <img src="/SiteAssets/Images/info.png"> falls outside the viewport.
The element <a href="/Pages/Info.aspx">Info</a> falls outside the viewport.
The element <input id="isSearchBox_S3…_InputKeywords" type="text" name="InputKeywords" class="ms-sbplain s4-…ox-QueryPrompt"> falls outside the viewport.
The element <a id="isSearchBox_S36190A05_go" href="javascript:S36190A05_Submit()"></a> falls outside the viewport.
The element <p>QUICK LINKS</p> falls outside the viewport.
The element <p>MOST PO***R</p> falls outside the viewport.
The element <a href="http://www.laf…s/default.aspx" class="mp-iLink">Animal Shelter &amp; Care Center</a> falls outside the viewport.
The element <a href="http://www.laf…topenings.aspx" class="mp-iLink">Employment Openings</a> falls outside the viewport.
The element <li>Pay Scale Listing</li> falls outside the viewport.
The element <li>Parks and Recreation</li> falls outside the viewport.
The element <li>Contact Us</li> falls outside the viewport.
The element <a href="http://www.laf…s/default.aspx" class="mp-iLink">Lafayette Police Department</a> falls outside the viewport.
The element <a href="http://www.laf…-commerce.aspx" class="mp-iLink">Chambers of Commerce</a> falls outside the viewport.
The element <a href="http://www.laf…s/default.aspx" class="mp-iLink">Lafayette City-Parish Council</a> falls outside the viewport.
The element <li>Flood Maps</li> falls outside the viewport.
The element <p>BUSINESS CENTER</p> falls outside the viewport.
The element <a href="http://lafayet…-Commerce.aspx" class="bc-iLink">Chambers of Commerce</a> falls outside the viewport.
The element <a href="http://lafayet…pplication.pdf" class="bc-iLink">Certificates of Occupancy</a> falls outside the viewport.
The element <li>eTrakIt</li> falls outside the viewport.
The element <a href="http://www.lecentre.org/" class="bc-iLink">Lafayette International Center</a> falls outside the viewport.
The element <a href="http://lafayet…terprise-.aspx" class="bc-iLink">Disadvantaged…ears 2020-2022</a> falls outside the viewport.
The element <a href="http://lafayet…ndpermits.aspx" class="bc-iLink">Permits and Applications</a> falls outside the viewport.
The element <a href="http://lafayet…s/default.aspx" class="bc-iLink">Development and Planning</a> falls outside the viewport.
The element <li>Sign Regulations</li> falls outside the viewport.
The element <li>more...</li> falls outside the viewport.
The element <p>CITY/PARISH SERVICES</p> falls outside the viewport.
The element <a href="http://lafayet…sed-Budget.pdf" class="cs-iLink">2019-2020 Proposed Budget</a> falls outside the viewport.
The element <a href="http://lafayet…esentation.pdf" class="cs-iLink">2019-2020 Prop…t Presentation</a> falls outside the viewport.
The element <a href="http://lafayet…Pages/FSS.aspx" class="cs-iLink">LFD Hearing Loss Smoke Alarms</a> falls outside the viewport.
The element <a href="http://lafayet…ne-Change.aspx" class="cs-iLink">Did your flood zone change?</a> falls outside the viewport.
The element <li>City-Parish Council</li> falls outside the viewport.
The element <a href="http://lafayet…cil-Agenda.pdf" class="cs-iLink">Council Agenda (Upcoming)</a> falls outside the viewport.
The element <a href="http://lafayet…UDGET-BOOK.pdf" class="cs-iLink">2018-2019 Adopted Budget</a> falls outside the viewport.
The element <a href="http://lafayet…s/default.aspx" class="cs-iLink">Development Services</a> falls outside the viewport.
The element <a href="http://lafayet…s/default.aspx" class="cs-iLink">Environmental Quality</a> falls outside the viewport.
The element <a href="https://lcg.ma…143376b9738bf8" class="cs-iLink">Find Your Council Member</a> falls outside the viewport.
The element <a href="http://lafayet…ollection.html" class="cs-iLink">Garbage/Curbside Collection</a> falls outside the viewport.
The element <li>Lafayette Transit</li> falls outside the viewport.
The element <a href="http://Snstaxp…com/cityoflaff" class="cs-iLink">Lookup City Tax Information</a> falls outside the viewport.
The element <li>Recycling</li> falls outside the viewport.
The element <li>Utilities</li> falls outside the viewport.
The element <li>more...</li> falls outside the viewport.
The element <div class="divSep1"> falls outside the viewport.
The element <div class="divSep2"> falls outside the viewport.
The element <div id="footerBox4Header">Connect With LCG</div> falls outside the viewport.
The element <a href="http://www.fac…66009026799663" class="fb3-Link">Facebook</a> falls outside the viewport.
The element <li>Twitter</li> falls outside the viewport.
The element <a href="http://instagr…ojectfrontyard" class="fb3-Link">Instagram</a> falls outside the viewport.
The element <a href="http://lafayet…ia-Center.aspx" class="fb3-mmLink">Social Media Center</a> falls outside the viewport.
The element <a href="http://lafayet…Directory.aspx">PHONE DIRECTORY</a> falls outside the viewport.

Reduce server response time

In our test, your server responded in 0.91 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 54.6KiB (53% reduction).

Compressing http://lafayettela.gov/SiteAssets/Images/lcg-logo.png could save 9KiB (33% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/Innovation-Image.png could save 7.2KiB (49% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/media-image.png could save 3.4KiB (71% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/search-button.png could save 3KiB (82% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/footer-rounded-boxes.png could save 3KiB (66% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/search-icon.png could save 3KiB (72% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/bottom-footer-navigation.png could save 2.9KiB (73% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/media-center.png could save 2.8KiB (63% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/services.png could save 2.6KiB (58% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/info.png could save 2.6KiB (59% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/departments.png could save 2.6KiB (59% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/Facebook-Icon.png could save 2.6KiB (72% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/Twitter-Icon.png could save 2.6KiB (72% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/calendar.png could save 2.5KiB (53% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/pay-online.png could save 2.4KiB (51% reduction).
Compressing http://lafayettela.gov/SiteAssets/Images/Instagram_Icon.png could save 2.3KiB (57% reduction).
Compressing http://lafayettela.gov/_layouts/images/gosearch15.png could save 117B (19% reduction).

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 36.2KiB (48% reduction).

Minifying http://lafayettela.gov/SiteAssets/js/jquery-1.8.0.js could save 35.7KiB (48% reduction) after compression.
Minifying http://lafayettela.gov/siteassets/js/touch-fix.js could save 588B (78% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 1.3KiB (12% reduction).

Minifying http://lafayettela.gov/Pages/Index.aspx could save 1.3KiB (12% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 882B (23% reduction).

Minifying http://lafayettela.gov/SiteAssets/CSS/lcg_master.css could save 882B (23% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does lafayettela.gov use compression?

lafayettela.gov use gzip compression.
Original size: 45.88 KB
Compressed size: 14.06 KB
File reduced by: 31.82 KB (69%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  93
Vendor reliability:
  93
Privacy:
  93
Child safety:
  93

+ SSL Checker - SSL Certificate Verify

lafayettela.gov supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.lafayettela.gov
Organization: Lafayette Consolidated Government
Location: Lafayette, Louisiana, US
Issuer: DigiCert SHA2 Secure Server CA
Valid from: Aug 8 00:00:00 2019 GMT
Valid until: Feb 26 12:00:00 2021 GMT
Authority: Is not a CA
Keysize:
Common Name: DigiCert SHA2 Secure Server CA
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root CA
Valid from: Mar 8 12:00:00 2013 GMT
Valid until: Mar 8 12:00:00 2023 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

lafayettela.gov does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Type: text/html; charset=UTF-8
Location: http://lafayettela.gov/Pages/Index.aspx
Server: Microsoft-IIS/7.5
SPRequestGuid: 39f6ec21-10e6-4139-8d68-d700fb3bcd58
X-SharePointHealthScore: 0
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 14.0.0.7105
X-MS-InvokeApp: 1; RequireReadOnly
Date: Mon, 28 Oct 2019 12:56:15 GMT
Content-Length: 162

HTTP/1.1 200 OK
Cache-Control: private, max-age=0
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
Expires: Sun, 13 Oct 2019 12:56:15 GMT
Last-Modified: Mon, 28 Oct 2019 12:56:15 GMT
Vary: Accept-Encoding
Server: Microsoft-IIS/7.5
SPRequestGuid: 110e68b7-c9d6-43ff-963a-dc989661a5a8
X-SharePointHealthScore: 0
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 14.0.0.7105
X-MS-InvokeApp: 1; RequireReadOnly
Date: Mon, 28 Oct 2019 12:56:15 GMT
Content-Length: 14402

+ DNS Lookup

Type Ip Target TTL
MX mail1.lafayettegov.net 3600
MX mail2.lafayettegov.net 3600
A 12.166.209.100 3600
SOA 3600
Mname ns1.lusfiber.net
Rname postmaster.lusfiber.net
Serial Number 2017062940
Refresh 10800
Retry 3600
Expire 2419200
Minimum TTL 0
TXT 3600
TXT 3600
NS ns1.lusfiber.net 3600
NS ns2.lusfiber.net 3600

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.dotgov.gov...
% DOTGOV WHOIS Server ready
Domain Name: LAFAYETTELA.GOV
Status: ACTIVE

>>> Last update of whois database: 2019-10-28T12:56:42Z <<<

Please be advised that this whois server only contains information pertaining
to the .GOV domain. For information for other domains please use the whois
server at RS.INTERNIC.NET.
Last update was 120 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with lafayettela.gov in any way. Only publicly available statistics data are displayed.
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
lafayettela.gov widget