3.6 sec in total
152 ms
3.3 sec
128 ms
Click here to check amazing Legacy LHH content for United States. Otherwise, check out these important facts you probably never knew about legacy.lhh.com
Visit legacy.lhh.comWe analyzed Legacy.lhh.com page load time and found that the first response time was 152 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
legacy.lhh.com performance score
name
value
score
weighting
Value27.9 s
0/100
10%
Value30.0 s
0/100
25%
Value56.0 s
0/100
10%
Value120 ms
97/100
30%
Value0.007
100/100
15%
Value30.2 s
0/100
10%
152 ms
36 ms
2199 ms
71 ms
77 ms
Our browser made a total of 194 requests to load all elements on the main page. We found that 97% of them (188 requests) were addressed to the original Legacy.lhh.com, 2% (3 requests) were made to Ajax.googleapis.com and 1% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Legacy.lhh.com.
Page size can be reduced by 61.2 kB (54%)
113.4 kB
52.2 kB
In fact, the total size of Legacy.lhh.com main page is 113.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. HTML takes 67.2 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.8 kB or 58% 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. Legacy LHH images are well optimized though.
Potential reduce by 22.4 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 22.4 kB or 50% of the original size.
Number of requests can be reduced by 176 (93%)
190
14
The browser has sent 190 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Legacy LHH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 177 to 1 for JavaScripts and as a result speed up the page load time.
legacy.lhh.com
152 ms
Login.aspx
36 ms
Login.aspx
2199 ms
refreshstyles
71 ms
PortalCSSHandler.ashx
77 ms
styles
125 ms
jquery.min.js
37 ms
jquery-ui.min.js
44 ms
jquery
128 ms
json2.min.js
92 ms
WebResource.axd
129 ms
ScriptResource.axd
93 ms
ScriptResource.axd
184 ms
ScriptResource.axd
157 ms
ScriptResource.axd
115 ms
ScriptResource.axd
139 ms
ScriptResource.axd
143 ms
ScriptResource.axd
142 ms
ScriptResource.axd
180 ms
ScriptResource.axd
181 ms
ScriptResource.axd
179 ms
ScriptResource.axd
182 ms
ScriptResource.axd
182 ms
ScriptResource.axd
193 ms
ScriptResource.axd
201 ms
ScriptResource.axd
201 ms
ScriptResource.axd
202 ms
ScriptResource.axd
205 ms
ScriptResource.axd
205 ms
ScriptResource.axd
215 ms
ScriptResource.axd
223 ms
ScriptResource.axd
225 ms
ScriptResource.axd
224 ms
ScriptResource.axd
271 ms
ScriptResource.axd
226 ms
ScriptResource.axd
239 ms
ScriptResource.axd
243 ms
ScriptResource.axd
245 ms
ScriptResource.axd
247 ms
ScriptResource.axd
245 ms
Render.aspx
214 ms
angular.min.js
16 ms
ScriptResource.axd
241 ms
ScriptResource.axd
215 ms
Login.aspx
248 ms
ScriptResource.axd
198 ms
ScriptResource.axd
198 ms
ScriptResource.axd
186 ms
ScriptResource.axd
183 ms
ScriptResource.axd
184 ms
ScriptResource.axd
185 ms
ScriptResource.axd
175 ms
ScriptResource.axd
220 ms
ScriptResource.axd
214 ms
ScriptResource.axd
213 ms
ScriptResource.axd
187 ms
ScriptResource.axd
179 ms
ScriptResource.axd
179 ms
ScriptResource.axd
180 ms
ScriptResource.axd
179 ms
ScriptResource.axd
180 ms
ScriptResource.axd
170 ms
ScriptResource.axd
164 ms
ScriptResource.axd
164 ms
ScriptResource.axd
180 ms
ScriptResource.axd
179 ms
ScriptResource.axd
179 ms
ScriptResource.axd
170 ms
ScriptResource.axd
164 ms
ScriptResource.axd
162 ms
ScriptResource.axd
164 ms
ScriptResource.axd
165 ms
ScriptResource.axd
152 ms
ScriptResource.axd
148 ms
ScriptResource.axd
148 ms
ScriptResource.axd
218 ms
ScriptResource.axd
216 ms
ScriptResource.axd
206 ms
ScriptResource.axd
201 ms
ScriptResource.axd
200 ms
ScriptResource.axd
200 ms
ScriptResource.axd
207 ms
ScriptResource.axd
195 ms
ScriptResource.axd
189 ms
ScriptResource.axd
185 ms
ScriptResource.axd
183 ms
ScriptResource.axd
184 ms
ScriptResource.axd
167 ms
ScriptResource.axd
158 ms
ScriptResource.axd
159 ms
ScriptResource.axd
161 ms
ScriptResource.axd
158 ms
ScriptResource.axd
155 ms
ScriptResource.axd
164 ms
ScriptResource.axd
165 ms
ScriptResource.axd
165 ms
ScriptResource.axd
165 ms
ScriptResource.axd
167 ms
ScriptResource.axd
167 ms
ScriptResource.axd
165 ms
ScriptResource.axd
163 ms
ScriptResource.axd
164 ms
ScriptResource.axd
163 ms
ScriptResource.axd
164 ms
ScriptResource.axd
164 ms
ScriptResource.axd
180 ms
ScriptResource.axd
180 ms
ScriptResource.axd
181 ms
ScriptResource.axd
181 ms
ScriptResource.axd
181 ms
ScriptResource.axd
182 ms
ga.js
88 ms
ScriptResource.axd
132 ms
ScriptResource.axd
130 ms
ScriptResource.axd
133 ms
ScriptResource.axd
131 ms
ScriptResource.axd
132 ms
ScriptResource.axd
133 ms
ScriptResource.axd
135 ms
ScriptResource.axd
132 ms
ScriptResource.axd
136 ms
ScriptResource.axd
136 ms
ScriptResource.axd
136 ms
ScriptResource.axd
138 ms
__utm.gif
22 ms
ScriptResource.axd
124 ms
ScriptResource.axd
124 ms
ScriptResource.axd
124 ms
ScriptResource.axd
124 ms
ScriptResource.axd
122 ms
ScriptResource.axd
124 ms
ScriptResource.axd
135 ms
ScriptResource.axd
134 ms
ScriptResource.axd
135 ms
ScriptResource.axd
133 ms
ScriptResource.axd
133 ms
ScriptResource.axd
131 ms
ScriptResource.axd
138 ms
ScriptResource.axd
138 ms
ScriptResource.axd
138 ms
ScriptResource.axd
136 ms
ScriptResource.axd
142 ms
ScriptResource.axd
141 ms
ScriptResource.axd
133 ms
ScriptResource.axd
133 ms
ScriptResource.axd
137 ms
ScriptResource.axd
159 ms
ScriptResource.axd
141 ms
ScriptResource.axd
136 ms
ScriptResource.axd
133 ms
ScriptResource.axd
130 ms
ScriptResource.axd
131 ms
ScriptResource.axd
149 ms
ScriptResource.axd
150 ms
ScriptResource.axd
150 ms
ScriptResource.axd
145 ms
ScriptResource.axd
146 ms
ScriptResource.axd
152 ms
ScriptResource.axd
154 ms
ScriptResource.axd
155 ms
ScriptResource.axd
158 ms
ScriptResource.axd
147 ms
ScriptResource.axd
147 ms
ScriptResource.axd
146 ms
ScriptResource.axd
147 ms
ScriptResource.axd
145 ms
ScriptResource.axd
164 ms
ScriptResource.axd
149 ms
ScriptResource.axd
156 ms
ScriptResource.axd
153 ms
ScriptResource.axd
160 ms
ScriptResource.axd
153 ms
ScriptResource.axd
163 ms
ScriptResource.axd
144 ms
ScriptResource.axd
166 ms
ScriptResource.axd
142 ms
ScriptResource.axd
159 ms
ScriptResource.axd
143 ms
ScriptResource.axd
164 ms
ScriptResource.axd
154 ms
ScriptResource.axd
152 ms
ScriptResource.axd
152 ms
ScriptResource.axd
147 ms
ScriptResource.axd
147 ms
WebResource.axd
143 ms
refresh
171 ms
ngdialog
124 ms
angulardirective
152 ms
angularfilters
151 ms
angularservices
148 ms
refreshapplication
148 ms
refreshmain
140 ms
equalizer
139 ms
lhh.png
144 ms
legacy.lhh.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
Form elements do not have associated labels
legacy.lhh.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
legacy.lhh.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Legacy.lhh.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 Legacy.lhh.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.
legacy.lhh.com
Open Graph description is not detected on the main page of Legacy LHH. 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: