Overview Review Traffic Revenue SEO
Hosting Registration Security Technical Related

linkedin.com

linkedin.com is SSL secured

Free website and domain report on linkedin.com

Last Updated: 31st March, 2024 Update Now
Overview

Snoop Summary for linkedin.com

This is a free and comprehensive report about linkedin.com. The domain linkedin.com is currently hosted on a server located in United States with the IP address 13.107.42.14, where the local currency is USD and English is the local language. Our records indicate that linkedin.com is owned/operated by LinkedIn Corporation. Linkedin.com is expected to earn an estimated $1,250,479 USD per day from advertising revenue. The sale of linkedin.com would possibly be worth $912,849,390 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Linkedin.com receives an estimated 90,511,592 unique visitors every day - an unbelievable amount of traffic! This report was last updated 31st March, 2024.

About linkedin.com

Site Preview: linkedin.com linkedin.com
Title: LinkedIn: Log In or Sign Up
Description: 1 billion members | Manage your professional identity. Build and engage with your professional network. Access knowledge, insights and opportunities.
Keywords and Tags: amazon, cnn, facebook, google, indeed, jobs, linked in, linkedin, linkedin jobs, linkedin learning, linkedin login, netflix, popular, professional networking, walmart, wells fargo, zillow
Related Terms: 750 ml to oz, leonard linkedin, linkedin cmo, linkedin premium, linkedin profile optimizaion, professional identity
Fav Icon:
Age: Over 22 years old
Domain Created: 2nd November, 2002
Domain Updated: 29th November, 2023
Domain Expires: 2nd November, 2024
Review

Snoop Score

5/5 (Perfect!)

Valuation

$912,849,390 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 16
Alexa Reach:
SEMrush Rank (US): 41
SEMrush Authority Score: 95
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 37,322,827 19,349
Traffic: 69,725,098 323,464
Cost: $108,945,999 USD $1,829,496 USD
Traffic

Visitors

Daily Visitors: 90,511,592
Monthly Visitors: 2,754,887,740
Yearly Visitors: 33,036,731,080
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1,250,479 USD
Monthly Revenue: $38,060,630 USD
Yearly Revenue: $456,424,690 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 8,870,436,951
Referring Domains: 6,557,670
Referring IPs: 1,990,000
Linkedin.com has 8,870,436,951 backlinks according to SEMrush. 67% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve linkedin.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of linkedin.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://careerbuilder.vn/
Target: https://www.linkedin.com/company/careerbuilder-vietnam
2
Source: https://ivrnet.com/
Target: https://www.linkedin.com/company/ivrnet/
3
Source: https://www.clickbank.com/
Target: https://www.linkedin.com/company/clickbank/
4
Source: https://www.hako.com/
Target: https://linkedin.com/company/hako-gmbh
5
Source: https://www.smg.com/
Target: https://www.linkedin.com/feed/update/urn:li:activity:6655736572081684482

Top Ranking Keywords (US)

1
Keyword: linkedin
Ranked Page: https://www.linkedin.com/
2
Keyword: linked in
Ranked Page: https://www.linkedin.com/
3
Keyword: amazon
Ranked Page: https://www.linkedin.com/company/amazon
4
Keyword: google
Ranked Page: https://www.linkedin.com/company/google
5
Keyword: jobs
Ranked Page: https://www.linkedin.com/jobs

Domain Analysis

Value Length
Domain: linkedin.com 12
Domain Name: linkedin 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 2.61 seconds
Load Time Comparison: Faster than 22% of sites

PageSpeed Insights

Avg. (All Categories) 79
Performance 99
Accessibility 100
Best Practices 83
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.linkedin.com/
Updated: 17th December, 2022

1.24 seconds
First Contentful Paint (FCP)
91%
6%
3%

0.01 seconds
First Input Delay (FID)
97%
2%
1%

Simulate loading on desktop
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for linkedin.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.8 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://linkedin.com/
http/1.1
0
34.922000020742
410
0
301
text/plain
https://www.linkedin.com/
h2
35.290000028908
282.81300002709
17022
116960
200
text/html
Document
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
h2
295.4299999401
361.23100016266
46256
328015
200
text/css
Stylesheet
https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4
h2
295.67700019106
341.17300016806
10075
27695
200
image/svg+xml
Image
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
h2
305.6630003266
367.91000002995
104305
360810
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
h2
306.00900016725
364.04599994421
57807
186844
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/8fkga714vy9b2wk5auqo5reeb
h2
507.62100005522
525.97799990326
2543
2958
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/5x5h6fkfoq2njo0ocxqr98mrk
h2
509.18700033799
527.19600033015
1580
384
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/7kb6sn3tm4cx918cx9a5jlb0
h2
510.49800030887
526.72300022095
1578
351
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/8wykgzgbqy0t3fnkgborvz54u
h2
511.60799991339
527.60200016201
1643
737
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/92eb1xekc34eklevj0io6x4ki
h2
512.78900029138
530.08799999952
1574
335
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/b4jgwnrrzl0qfc47qjfws95pj
h2
513.38799996302
528.87800009921
1780
820
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/ddi43qwelxeqjxdd45pe3fvs1
h2
515.13000018895
530.67500004545
2243
2435
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/4chtt12k98xwnba1nimld2oyg
h2
515.8080002293
531.23900014907
1497
201
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/ddi43qwelxeqjxdd45pe3fvs1
h2
516.58200006932
531.69699991122
2243
2435
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
h2
517.65100006014
542.13500022888
39992
110152
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
h2
518.40900024399
554.3300001882
73362
223236
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
h2
529.34300014749
678.2830003649
1089
0
200
text/css
Fetch
https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4
h2
529.62800022215
590.30200028792
1320
0
200
image/svg+xml
Fetch
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
h2
529.86100036651
590.47299996018
1025
0
200
text/javascript
Fetch
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
h2
530.54099995643
594.40700011328
1323
0
200
text/javascript
Fetch
https://www.linkedin.com/homepage-guest/api/ingraphs/gauge
h2
547.22500033677
627.36100004986
2637
0
200
text/plain
XHR
https://www.linkedin.com/litms/api/metadata/user
h2
557.15300003067
651.38200018555
1893
344
200
application/json
XHR
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
h2
559.00599993765
614.0340003185
43447
140173
200
application/javascript
Script
https://static.licdn.com/aero-v1/sc/h/8fkga714vy9b2wk5auqo5reeb
h2
570.91100001708
594.71400035545
1318
0
200
image/svg+xml
Fetch
https://accounts.google.com/o/oauth2/iframe
h2
628.42399999499
638.1240002811
1784
283
200
text/html
Document
https://www.linkedin.com/li/track
h2
642.26600015536
759.03500011191
1685
0
200
text/plain
Fetch
https://accounts.google.com/gsi/status?client_id=990339570472-k6nqn1tpmitg8pui82bfaun3jrpmiuhs.apps.googleusercontent.com&as=k%2B17lfz%2FWk7TyXLxMRVKGQ
h2
665.70800030604
684.45500032976
1452
40
200
application/json
XHR
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
h2
677.88200033829
683.99700010195
36196
102440
200
text/javascript
Script
https://www.linkedin.com/homepage-guest/api/ingraphs/counter
h2
707.40099996328
799.17400004342
2637
0
200
text/plain
XHR
https://dpm.demdex.net/id?d_visid_ver=5.1.1&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_orgid=14215E3D5995C57C0A495C55%40AdobeOrg&d_nsid=0&ts=1671252531247
http/1.1
729.04499992728
799.54300029203
1261
611
200
application/json
XHR
https://accounts.google.com/o/oauth2/iframerpc?action=checkOrigin&origin=https%3A%2F%2Fwww.linkedin.com&client_id=990339570472-k6nqn1tpmitg8pui82bfaun3jrpmiuhs.apps.googleusercontent.com
h2
767.66500016674
784.13600008935
2176
49
200
application/json
XHR
https://www.linkedin.com/li/track
h2
798.41900011525
871.50300014764
1685
0
200
text/plain
Fetch
https://lnkd.demdex.net/dest5.html?d_nsid=0
http/1.1
813.85400006548
936.05699995533
3471
6983
200
text/html
Document
https://lnkd.demdex.net/event?d_dil_ver=9.4&_ts=1671252531254
http/1.1
817.64200003818
933.27100016177
1274
689
200
application/json
XHR
https://www.linkedin.com/li/track
h2
878.70400026441
963.36799999699
1719
0
200
text/plain
Fetch
https://lnkd.demdex.net/event?d_dil_ver=9.4&_ts=1671252531259
http/1.1
941.04800000787
1072.6450001821
1276
689
200
application/json
XHR
https://www.facebook.com/tr/?id=136430647058082&ev=Adobe-Audience-Manager-Segment&cd[segID]=16675012&noscript=1
h2
961.48700034246
975.18700035289
328
0
200
text/plain
Image
https://cm.g.doubleclick.net/pixel?google_nid=adobe_dmp&google_cm&gdpr=0&gdpr_consent=&google_hm=ODA1NzQ5MTEzMTc1MjkyNjg0MDEwMTE2MzA1NDMzMjQ3NjI0MDc=
http/1.1
1063.6189999059
1072.7079999633
1034
0
302
text/html
https://cm.g.doubleclick.net/pixel?google_nid=adobe_dmp&google_cm=&gdpr=0&gdpr_consent=&google_hm=ODA1NzQ5MTEzMTc1MjkyNjg0MDEwMTE2MzA1NDMzMjQ3NjI0MDc=&google_tc=
http/1.1
1073.4040001407
1083.117000293
1148
0
302
text/html
https://dpm.demdex.net/ibs:dpid=771&dpuuid=CAESEL1GGM-sjF088PobE-dE2TU&google_cver=1?gdpr=0&gdpr_consent=
http/1.1
1083.4630001336
1153.4710000269
940
42
200
image/gif
Image
https://www.linkedin.com/li/track
h2
1104.9040001817
1186.0030000098
1719
0
200
text/plain
Fetch
https://analytics.twitter.com/i/adsct?p_user_id=80574911317529268401011630543324762407&p_id=38594
http/1.1
1165.4710001312
1192.966000177
595
43
200
image/gif
Image
https://www.linkedin.com/li/track
h2
2595.4619999975
2672.3319999874
1685
0
200
text/plain
Fetch
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
290.452
12.929
343.145
7.737
363.511
9.523
373.894
51.755
431.358
21.625
453.065
5.912
459.311
42.202
506.075
13.91
519.998
44.008
598.573
29.33
631.247
10.021
643.05
23.534
670.018
8.238
679.74
21.9
708.454
33.559
744.498
6.453
752.254
7.904
791.247
8.584
804.574
15.563
935.422
6.898
943.084
8.076
1084.765
21.397
2577.631
18.938
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Linkedin.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Linkedin.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Linkedin.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Linkedin.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Linkedin.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 250 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.linkedin.com/
248.516
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Linkedin.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://linkedin.com/
190
https://www.linkedin.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Linkedin.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
8039
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
7824
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
7277
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
67
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
58
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4
0
Avoids enormous network payloads — Total size was 473 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
104305
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
73362
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
57807
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
46256
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
43447
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
39992
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
36196
https://www.linkedin.com/
17022
https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4
10075
https://lnkd.demdex.net/dest5.html?d_nsid=0
3471
Avoids an excessive DOM size — 603 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
603
Maximum DOM Depth
Training and Education
15
Maximum Child Elements
Training and Education …
35
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Linkedin.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.3 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
166.128
146.136
4.071
https://www.linkedin.com/
109.041
4.491
1.579
Unattributable
106.817
2.472
0
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
84.91
77.588
2.15
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
50.787
45.57
2.413
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
386.159
Other
150.935
Style & Layout
61.941
Script Parsing & Compilation
29.534
Rendering
27.281
Parse HTML & CSS
17.333
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 44 requests • 473 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
44
484027
Script
6
355109
Other
30
48447
Stylesheet
1
46256
Document
3
22277
Image
4
11938
Media
0
0
Font
0
0
Third-party
33
407488
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
43447
0
SHOW DETAILS
36196
0
SHOW DETAILS
8222
0
SHOW DETAILS
5412
0
SHOW DETAILS
2182
0
SHOW DETAILS
595
0
SHOW DETAILS
328
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Welcome to your professional community
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Welcome to your professional community
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Eliminate render-blocking resources — Potential savings of 200 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Linkedin.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
46256
310
Reduce unused JavaScript — Potential savings of 193 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
104305
74910
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
73362
43356
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
57807
31903
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
36196
24946
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
39992
22353
Serve static assets with an efficient cache policy — 8 resources found
Linkedin.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.facebook.com/tr/?id=136430647058082&ev=Adobe-Audience-Manager-Segment&cd[segID]=16675012&noscript=1
0
328
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
300000
43447
https://static.licdn.com/aero-v1/sc/h/9q42psw84tv933tbvwqoe327v
604800000
104305
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
604800000
73362
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
604800000
57807
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
604800000
46256
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
604800000
39992
https://static.licdn.com/aero-v1/sc/h/dxf91zhqd2z6b0bwg85ktm5s4
604800000
10075

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of linkedin.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Linkedin.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
83

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that linkedin.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
Consider adding 'unsafe-inline' (ignored by browsers supporting nonces/hashes) to be backward compatible with older browsers.
script-src
Medium

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://linkedin.com/
Allowed

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
...
SHOW DETAILS
...
SHOW DETAILS
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for linkedin.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source
SHOW DETAILS

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
22

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of linkedin.com. This includes details about web app manifests.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 80
Performance 81
Accessibility 100
Best Practices 75
SEO 93
PWA 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.linkedin.com/
Updated: 17th December, 2022

1.34 seconds
First Contentful Paint (FCP)
87%
9%
4%

0.02 seconds
First Input Delay (FID)
96%
3%
1%

Simulate loading on mobile
81

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for linkedin.com. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Speed Index — 2.7 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Properly size images
Images can slow down the page's load time. Linkedin.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Linkedin.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Linkedin.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Linkedin.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Linkedin.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.linkedin.com/
224.687
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Linkedin.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://linkedin.com/
630
https://www.linkedin.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Linkedin.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 471 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
100869
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
75398
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
57807
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
46256
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
43401
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
39992
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
36196
https://www.linkedin.com/
17555
https://static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn
9402
https://lnkd.demdex.net/dest5.html?d_nsid=0
3448
Avoids an excessive DOM size — 596 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
596
Maximum DOM Depth
button.modal__dismiss > icon.modal__dismiss-icon > svg.artdeco-icon > path
18
Maximum Child Elements
Business Analysis and Strategy 810+ courses
35
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Linkedin.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 43 requests • 471 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
43
482304
Script
6
353663
Other
29
48162
Stylesheet
1
46256
Document
3
22958
Image
4
11265
Media
0
0
Font
0
0
Third-party
32
404023
Minimize third-party usage — Third-party code blocked the main thread for 80 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
SHOW DETAILS
43401
84.716
SHOW DETAILS
36196
0
SHOW DETAILS
8204
0
SHOW DETAILS
5412
0
SHOW DETAILS
2182
0
SHOW DETAILS
595
0
SHOW DETAILS
328
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Welcome to your professional community
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 11 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
7698
202
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
1853
147
https://lnkd.demdex.net/dest5.html?d_nsid=0
4010
120
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
6076
109
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
5296
96
https://www.linkedin.com/
1612
82
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
1694
78
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
7140
65
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
1772
59
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
5190
56
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
5246
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.
Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Audits

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://linkedin.com/
http/1.1
0
61.067000031471
414
0
301
text/plain
https://www.linkedin.com/
h2
61.418000026606
285.1119999541
17555
116707
200
text/html
Document
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
h2
299.97699998785
333.29899993259
46256
328015
200
text/css
Stylesheet
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
h2
300.20199995488
329.03999998234
100869
343573
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
h2
304.69899997115
330.6009999942
57807
186844
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn
h2
383.49799998105
402.16099994723
9402
26291
200
image/svg+xml
Image
https://static.licdn.com/aero-v1/sc/h/8fkga714vy9b2wk5auqo5reeb
h2
449.37399995979
470.69500002544
2543
2958
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/b4jgwnrrzl0qfc47qjfws95pj
h2
449.84699995257
465.25599993765
1780
820
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/ddi43qwelxeqjxdd45pe3fvs1
h2
451.29100000486
467.15499996208
2243
2435
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/4chtt12k98xwnba1nimld2oyg
h2
451.75200002268
471.70100000221
1497
201
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/gs508lg3t2o81tq7pmcgn6m2
h2
452.35499995761
469.654000015
1521
274
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/ddi43qwelxeqjxdd45pe3fvs1
h2
453.50599999074
471.94199997466
2243
2435
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/4zqr0f9jf98vi2nkijyc3bex2
h2
453.92400003038
474.32999999728
1662
571
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/6q80tkax3uzufdiuwyfyush3p
h2
454.7859999584
472.13499993086
1820
922
200
image/svg+xml
XHR
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
h2
456.38500002678
475.0729999505
39992
110152
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
h2
456.81000000332
521.08700003009
75398
223236
200
text/javascript
Script
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
h2
464.850999997
593.13599998131
1119
0
200
text/css
Fetch
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
h2
465.13899997808
513.63900001161
1025
0
200
text/javascript
Fetch
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
h2
465.94299993012
513.72799999081
1323
0
200
text/javascript
Fetch
https://static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn
h2
466.32400003728
513.81099992432
1288
0
200
image/svg+xml
Fetch
https://www.linkedin.com/homepage-guest/api/ingraphs/gauge
h2
480.29600002337
559.38799993601
2637
0
200
text/plain
XHR
https://www.linkedin.com/homepage-guest/manifest.json
h2
488.72299992945
580.45499993023
3009
336
200
application/json
Manifest
https://www.linkedin.com/litms/api/metadata/user
h2
489.83400000725
575.91799995862
1854
337
200
application/json
XHR
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
h2
490.98799994681
602.08700003568
43401
140173
200
application/javascript
Script
https://static.licdn.com/aero-v1/sc/h/8fkga714vy9b2wk5auqo5reeb
h2
505.22399996407
544.21500000171
1318
0
200
image/svg+xml
Fetch
https://accounts.google.com/o/oauth2/iframe
h2
542.59999992792
554.23499993049
1955
283
200
text/html
Document
https://www.linkedin.com/li/track
h2
562.60199996177
668.53000002448
1685
0
200
text/plain
Fetch
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
h2
573.77899996936
578.56199995149
36196
102440
200
text/javascript
Script
https://accounts.google.com/gsi/status?client_id=990339570472-k6nqn1tpmitg8pui82bfaun3jrpmiuhs.apps.googleusercontent.com&as=ofEo4MnSyheqjE2PzvHcGQ
h2
593.16599997692
622.23700003233
1452
40
200
application/json
XHR
https://accounts.google.com/o/oauth2/iframerpc?action=checkOrigin&origin=https%3A%2F%2Fwww.linkedin.com&client_id=990339570472-k6nqn1tpmitg8pui82bfaun3jrpmiuhs.apps.googleusercontent.com
h2
616.38100002892
629.71699994523
2005
49
200
application/json
XHR
https://www.linkedin.com/homepage-guest/api/ingraphs/counter
h2
634.22200002242
724.61399994791
2637
0
200
text/plain
XHR
https://dpm.demdex.net/id?d_visid_ver=5.1.1&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_orgid=14215E3D5995C57C0A495C55%40AdobeOrg&d_nsid=0&ts=1671252547550
http/1.1
651.97599993553
724.27100001369
1261
611
200
application/json
XHR
https://www.linkedin.com/li/track
h2
734.30499993265
812.203999958
1685
0
200
text/plain
Fetch
https://lnkd.demdex.net/dest5.html?d_nsid=0
http/1.1
764.13999998476
858.14100003336
3448
6983
200
text/html
Document
https://lnkd.demdex.net/event?d_dil_ver=9.4&_ts=1671252547556
http/1.1
765.7139999792
884.48200002313
1277
689
200
application/json
XHR
https://lnkd.demdex.net/event?d_dil_ver=9.4&_ts=1671252547559
http/1.1
908.22600002866
1025.0430000015
1278
689
200
application/json
XHR
https://www.facebook.com/tr/?id=136430647058082&ev=Adobe-Audience-Manager-Segment&cd[segID]=16675012&noscript=1
h2
933.06399998255
947.95800000429
328
0
200
text/plain
Image
https://www.linkedin.com/li/track
h2
1044.162999955
1123.1200000038
1719
0
200
text/plain
Fetch
https://cm.g.doubleclick.net/pixel?google_nid=adobe_dmp&google_cm&gdpr=0&gdpr_consent=&google_hm=NTUzNDkwNDkwNTM0MTY4NTA4ODAyMTIxNDkyNDQxNTE5NjA2NDI=
http/1.1
1053.6970000248
1061.9489999954
1034
0
302
text/html
https://cm.g.doubleclick.net/pixel?google_nid=adobe_dmp&google_cm=&gdpr=0&gdpr_consent=&google_hm=NTUzNDkwNDkwNTM0MTY4NTA4ODAyMTIxNDkyNDQxNTE5NjA2NDI=&google_tc=
http/1.1
1062.2809999622
1071.5119999368
1148
0
302
text/html
https://dpm.demdex.net/ibs:dpid=771&dpuuid=CAESEN50p2DxxzFmDkV8lRsnYo0&google_cver=1?gdpr=0&gdpr_consent=
http/1.1
1071.7549999245
1145.4359999625
940
42
200
image/gif
Image
https://analytics.twitter.com/i/adsct?p_user_id=55349049053416850880212149244151960642&p_id=38594
http/1.1
1158.9769999264
1191.3260000292
595
43
200
image/gif
Image
https://www.linkedin.com/li/track
h2
2572.7389999665
2663.9689999865
1685
0
200
text/plain
Fetch
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
292.636
11.321
335.35
7.71
344.414
40.961
385.434
19.608
407.581
5.22
412.837
29.633
447.664
10.773
458.447
36.761
522.149
20.956
555.308
8.867
564.187
11.076
578.253
16.236
617.531
13.889
636.352
24.914
685.021
5.17
725.138
10.713
740.487
27.357
805.796
6.812
869.53
30.052
900.468
8.534
909.065
5.41
914.679
11.605
1021.739
24.01
1147.807
5.811
1155
5.277
1818.213
9.458
2463.13
7.337
2520.003
50.497
2981.09
7.011
3085.004
8.807
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

First Contentful Paint — 2.6 s
The time taken for the first image or text on the page to be rendered.
Total Blocking Time — 270 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 2.8 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 200 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.6 s
The time taken for the primary content of the page to be rendered.

Other

Eliminate render-blocking resources — Potential savings of 690 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Linkedin.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
46256
1080
Avoid serving legacy JavaScript to modern browsers — Potential savings of 23 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
8039
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
7824
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
7479
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
67
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
59
Serve static assets with an efficient cache policy — 8 resources found
Linkedin.com can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://www.facebook.com/tr/?id=136430647058082&ev=Adobe-Audience-Manager-Segment&cd[segID]=16675012&noscript=1
0
328
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
300000
43401
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
604800000
100869
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
604800000
75398
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
604800000
57807
https://static.licdn.com/aero-v1/sc/h/86zy6pk2bnlnkpgdsvll6f113
604800000
46256
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
604800000
39992
https://static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn
604800000
9402
Reduce JavaScript execution time — 1.6 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
734.632
635.224
12.76
Unattributable
617.552
27.728
0
https://www.linkedin.com/
447.324
27.496
5.028
https://platform.linkedin.com/litms/utag/homepage-guest-frontend/utag.js?cb=1671252300000
333.916
295.784
7.84
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
249.68
232.336
5.92
https://lnkd.demdex.net/dest5.html?d_nsid=0
173.376
65.332
28.544
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
123.672
98.3
19.736
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
106.236
90.42
9.56
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
63.64
49.664
13.188
Minimize main-thread work — 3.0 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1570.992
Other
850.452
Style & Layout
235.496
Rendering
155.412
Script Parsing & Compilation
110.452
Parse HTML & CSS
59.26

Metrics

Time to Interactive — 7.6 s
The time taken for the page to become fully interactive.

Other

Reduce unused JavaScript — Potential savings of 189 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://static.licdn.com/aero-v1/sc/h/64m2jjp8xub8sum2ip5lg6vb8
100869
70009
https://static.licdn.com/aero-v1/sc/h/98lptr8kagfxge22q7k1fps8
75398
44560
https://static.licdn.com/aero-v1/sc/h/7dzsoyz1bsr7e64b321m3tjgi
57807
31522
https://www.gstatic.com/_/mss/boq-identity/_/js/k=boq-identity.IdpIFrameHttp.en_US.KfbFqosJV-Y.es5.O/d=1/rs=AOaEmlFUFFjuRV_Tr8tZDNBAzV7gWJKaBA/m=base
36196
24946
https://static.licdn.com/aero-v1/sc/h/etkd25e7kzp2lrg1w9y0kixlu
39992
22353
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
SHOW DETAILS
SHOW DETAILS
First Contentful Paint (3G) — 5190 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
100

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of linkedin.com. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have alternate text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Contrast

Background and foreground colors have a sufficient contrast ratio
Many (if not most) users find low-contrast text difficult or impossible to read.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Linkedin.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
75

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that linkedin.com should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
Consider adding 'unsafe-inline' (ignored by browsers supporting nonces/hashes) to be backward compatible with older browsers.
script-src
Medium

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://linkedin.com/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://static.licdn.com/aero-v1/sc/h/d58zfe6h3ycgq5l1ccjpkrtdn
374 x 214 (1.75)
340 x 272 (1.25)

Audits

Uses deprecated APIs — 2 warnings found
Avoid deprecated APIs which will eventually be removed the browser.
Deprecation / Warning Source
...
SHOW DETAILS
...
SHOW DETAILS
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for linkedin.com. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.
Document uses legible font sizes — 100% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
SHOW DETAILS
100.00%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source
SHOW DETAILS

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
50

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of linkedin.com. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of linkedin.com on mobile screens.

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 13.107.42.14
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Microsoft Corporation
Registration

Domain Registrant

Private Registration: No
Name: Host Master
Organization: LinkedIn Corporation
Country: US
City: Sunnyvale
State: CA
Post Code: 94085
Email: hostmaster@linkedin.com
Phone: +1.6506873600
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
MarkMonitor, Inc. 172.64.148.104
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Unknown
WOT Rating:
WOT Trustworthiness: 93/100
WOT Child Safety: 93/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: www.linkedin.com
Issued By: DigiCert SHA2 Secure Server CA
Valid From: 30th January, 2024
Valid To: 30th July, 2024
Subject: CN = www.linkedin.com
O = LinkedIn Corporation
L = Sunnyvale
S = US
Hash: 7459c5a1
Issuer: CN = DigiCert SHA2 Secure Server CA
O = DigiCert Inc
S = US
Version: 2
Serial Number: 4865841569784388953547465824704106742
Serial Number (Hex): 03A92082F7683C929F31CEA6DDEB90F6
Valid From: 30th January, 2024
Valid To: 30th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:0F:80:61:1C:82:31:61:D5:2F:28:E7:8D:46:38:B4:2C:E1:C6:D9:E2
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/DigicertSHA2SecureServerCA-1.crl

Full Name:
URI:http://crl4.digicert.com/DigicertSHA2SecureServerCA-1.crl
Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS
Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/DigiCertSHA2SecureServerCA-2.crt
SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Jan 30 04:49:02.623 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8D:ED:11:67:F2:AA:60:8D:7B:B3:33:
FD:5A:D8:FE:28:BF:EB:A2:D6:81:36:74:98:F5:90:08:
97:08:97:3F:61:02:20:5B:76:99:60:C6:25:32:C0:04:
39:02:68:66:81:DD:41:0A:38:3F:AB:EF:CF:2A:BB:23:
F1:8F:8C:09:45:EF:82
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Jan 30 04:49:02.626 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:C1:74:73:A6:D1:CA:25:FA:56:03:D6:
CE:8D:A8:1D:20:D1:2A:41:53:CC:69:D0:C9:1A:7E:81:
8C:68:8B:75:FE:02:20:11:3D:88:5E:54:C4:FA:AB:F3:
F3:BB:15:97:B0:55:0B:C5:BC:50:9C:F1:D7:8D:0D:25:
61:DB:D7:DF:DC:20:7C
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DA:B6:BF:6B:3F:B5:B6:22:9F:9B:C2:BB:5C:6B:E8:70:
91:71:6C:BB:51:84:85:34:BD:A4:3D:30:48:D7:FB:AB
Timestamp : Jan 30 04:49:02.616 2024 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:8E:ED:6D:4E:53:9A:07:90:AB:7B:7C:
35:E0:3D:CD:07:A7:A7:EA:9B:7C:FF:2B:C5:A5:B1:C5:
81:6A:0D:19:EA:02:20:6C:FF:41:9C:0E:95:92:89:CF:
F1:A3:93:86:50:64:9A:67:E4:AB:49:24:07:0E:9F:89:
0E:E1:81:BF:9A:82:30
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:afd.perf.linkedin.com
DNS:dc.ads.linkedin.com
DNS:exp1.www.linkedin.com
DNS:exp2.www.linkedin.com
DNS:exp3.www.linkedin.com
DNS:exp4.www.linkedin.com
DNS:exp5.www.linkedin.com
DNS:lan.sdk.linkedin.com
DNS:linkedin.com
DNS:lnkd.in
DNS:mid4.linkedin.com
DNS:payment.www.linkedin.com
DNS:px.ads.linkedin.com
DNS:px.jobs.linkedin.com
DNS:px4.ads.linkedin.com
DNS:realtime.www.linkedin.com
DNS:rum14.perf.linkedin.com
DNS:rum17.perf.linkedin.com
DNS:rum18.perf.linkedin.com
DNS:rum19.perf.linkedin.com
DNS:rum2.perf.linkedin.com
DNS:rum4.perf.linkedin.com
DNS:rum5.perf.linkedin.com
DNS:rum6.perf.linkedin.com
DNS:rum8.perf.linkedin.com
DNS:rum9.perf.linkedin.com
DNS:status.linkedin.com
DNS:www.linkedin-measure.com
DNS:www.linkedin.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
linkedin.com. 13.107.42.14 IN 300

HTTP Response Headers

HTTP-Code: HTTP/2 200
cache-control: no-cache, no-store
content-type: text/html; charset=utf-8
expires: 1st January, 1970
date: 31st March, 2024
pragma: no-cache
content-length: 134860
set-cookie: *
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
x-frame-options: sameorigin
content-security-policy: default-src 'none'; connect-src 'self' *.licdn.com *.linkedin.com cdn.linkedin.oribi.io dpm.demdex.net/id lnkd.demdex.net blob
x-li-fabric: prod-lor1
report-to: {"group":"network-errors","max_age":2592000,"endpoints":[{"url":"https://www.linkedin.com/li/rep"}],"include_subdomains":true}
nel: {"report_to":"network-errors","max_age":1296000,"success_fraction":0.00066,"failure_fraction":1,"include_subdomains":true}
x-li-pop: afd-prod-lor1-x
x-li-proto: http/2
x-li-uuid: AAYU+E5AMSN3fuLjK08FeA==
x-cache: CONFIG_NOCACHE
x-msedge-ref: Ref A

Whois Lookup

Created: 2nd November, 2002
Changed: 29th November, 2023
Expires: 2nd November, 2024
Registrar: MarkMonitor, Inc.
Status: clientUpdateProhibited
clientTransferProhibited
clientDeleteProhibited
serverUpdateProhibited
serverTransferProhibited
serverDeleteProhibited
Nameservers: dns1.p09.nsone.net
dns2.p09.nsone.net
dns3.p09.nsone.net
dns4.p09.nsone.net
ns1-42.azure-dns.com
ns2-42.azure-dns.net
ns3-42.azure-dns.org
ns4-42.azure-dns.info
Owner Name: Domain Administrator
Owner Organization: LinkedIn Corporation
Owner Street: 1000 W. Maude Ave
Owner Post Code: 94085
Owner City: Sunnyvale
Owner State: CA
Owner Country: US
Owner Phone: +1.6506873600
Owner Email: hostmaster@linkedin.com
Admin Name: Domain Administrator
Admin Organization: LinkedIn Corporation
Admin Street: 1000 W. Maude Ave
Admin Post Code: 94085
Admin City: Sunnyvale
Admin State: CA
Admin Country: US
Admin Phone: +1.6506873600
Admin Email: hostmaster@linkedin.com
Tech Name: Domain Administrator
Tech Organization: LinkedIn Corporation
Tech Street: 1000 W. Maude Ave
Tech Post Code: 94085
Tech City: Sunnyvale
Tech State: CA
Tech Country: US
Tech Phone: +1.6506873600
Tech Email: hostmaster@linkedin.com
Full Whois: Domain Name: linkedin.com
Registry Domain ID: 91818680_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2023-11-29T19:30:42+0000
Creation Date: 2002-11-02T15:38:11+0000
Registrar Registration Expiration Date: 2024-11-02T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: abusecomplaints@markmonitor.com
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: LinkedIn Corporation
Registrant Street: 1000 W. Maude Ave
Registrant City: Sunnyvale
Registrant State/Province: CA
Registrant Postal Code: 94085
Registrant Country: US
Registrant Phone: +1.6506873600
Registrant Phone Ext:
Registrant Fax: +1.6506870505
Registrant Fax Ext:
Registrant Email: hostmaster@linkedin.com
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: LinkedIn Corporation
Admin Street: 1000 W. Maude Ave
Admin City: Sunnyvale
Admin State/Province: CA
Admin Postal Code: 94085
Admin Country: US
Admin Phone: +1.6506873600
Admin Phone Ext:
Admin Fax: +1.6506870505
Admin Fax Ext:
Admin Email: hostmaster@linkedin.com
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: LinkedIn Corporation
Tech Street: 1000 W. Maude Ave
Tech City: Sunnyvale
Tech State/Province: CA
Tech Postal Code: 94085
Tech Country: US
Tech Phone: +1.6506873600
Tech Phone Ext:
Tech Fax: +1.6506870505
Tech Fax Ext:
Tech Email: hostmaster@linkedin.com
Name Server: dns4.p09.nsone.net
Name Server: ns1-42.azure-dns.com
Name Server: ns4-42.azure-dns.info
Name Server: ns3-42.azure-dns.org
Name Server: dns3.p09.nsone.net
Name Server: ns2-42.azure-dns.net
Name Server: dns1.p09.nsone.net
Name Server: dns2.p09.nsone.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-31T17:34:26+0000 <<<

For more information on WHOIS status codes, please visit:
https://www.icann.org/resources/pages/epp-status-codes

If you wish to contact this domain’s Registrant, Administrative, or Technical
contact, and such email address is not visible above, you may do so via our web
form, pursuant to ICANN’s Temporary Specification. To verify that you are not a
robot, please enter your email address to receive a link to a page that
facilitates email communication with the relevant contact(s).

Web-based WHOIS:
https://domains.markmonitor.com/whois

If you have a legitimate interest in viewing the non-public WHOIS details, send
your request and the reasons for your request to whoisrequest@markmonitor.com
and specify the domain name in the subject line. We will review that request and
may ask for supporting documentation and explanation.

The data in MarkMonitor’s WHOIS database is provided for information purposes,
and to assist persons in obtaining information about or related to a domain
name’s registration record. While MarkMonitor believes the data to be accurate,
the data is provided "as is" with no guarantee or warranties regarding its
accuracy.

By submitting a WHOIS query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to:
(1) allow, enable, or otherwise support the transmission by email, telephone,
or facsimile of mass, unsolicited, commercial advertising, or spam; or
(2) enable high volume, automated, or electronic processes that send queries,
data, or email to MarkMonitor (or its systems) or the domain name contacts (or
its systems).

MarkMonitor reserves the right to modify these terms at any time.

By submitting this query, you agree to abide by this policy.

MarkMonitor Domain Management(TM)
Protecting companies and consumers in a digital world.

Visit MarkMonitor at https://www.markmonitor.com
Contact us at +1.8007459229
In Europe, at +44.02032062220
----
View Raw Whois

Nameservers

Name IP Address
dns1.p09.nsone.net 198.51.44.9
dns2.p09.nsone.net 198.51.45.9
dns3.p09.nsone.net 198.51.44.73
dns4.p09.nsone.net 198.51.45.73
ns1-42.azure-dns.com 150.171.10.42
ns2-42.azure-dns.net 150.171.16.42
ns3-42.azure-dns.org 13.107.222.42
ns4-42.azure-dns.info 13.107.206.42
Related

Subdomains

Domain Subdomain
ads.linkedin.com
ads
ae.linkedin.com
ae
au.linkedin.com
au
bd.linkedin.com
bd
blog.linkedin.com
blog
All linkedin.com subdomains

Similar Sites

Domain Valuation Snoop Score
friendster.com
$971 USD 1/5
google.com
$4,794,933,151 USD 5/5
match.com
$3,410,891 USD 4/5
meetup.com
$11,303,449 USD 5/5
myspace.com
$1,602,740 USD 4/5
All sites similar to linkedin.com

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
linkedin.co
0/5
linkedin.net
0/5
linkedin.nl
0/5
linkedin.ru
$10 USD

Sites hosted on the same IP address

Love W3 Snoop?
Update Now

linkedin.com Infographic

linkedin.com by the numbers infographic

Recently Updated

nontonsegar.net
jharaphula.com
pinoymovieshub.to
kimoitv.com
now.gg
totalbypass.info
google.com
youtube.com
filedrive.com
findglocal.com

Recently Viewed

phone-size.com
lesedsed.com
retro-mu.com
perthwaterfront.com
netmutfak.com
bux3.cn
pianhao.com
pocket-arts.com
ridingo.com
riskmcs.com