up.com

up.com is SSL secured

Free website and domain report on up.com

Last Updated: 13th June, 2023 Update Now
Overview

Snoop Summary for up.com

This is a free and comprehensive report about up.com. Up.com has the potential to be earning an estimated $13 USD per day from advertising revenue. If up.com was to be sold it would possibly be worth $9,418 USD (based on the daily revenue potential of the website over a 24 month period). Up.com is quite popular with an estimated 4,522 daily unique visitors. This report was last updated 13th June, 2023.

About up.com

Site Preview: up.com up.com
Title: Union Pacific
Description: Union Pacific operates North America's premier railroad franchise, covering 23 states in the western two-thirds of the United States.
Keywords and Tags: business
Related Terms: 2 states, 50 states, cathay pacific, jetstar pacific, pacific union college, rule of thirds, sporcle us states, states abbreviations, us states, western united states
Fav Icon:
Age: Over 30 years old
Domain Created: 12th May, 1994
Domain Updated: 23rd December, 2020
Domain Expires: 13th May, 2022
Review

Snoop Score

3/5 (Great!)

Valuation

$9,418 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 135,825
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 4,522
Monthly Visitors: 137,636
Yearly Visitors: 1,650,536
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $13 USD
Monthly Revenue: $392 USD
Yearly Revenue: $4,704 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: up.com 6
Domain Name: up 2
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.02 seconds
Load Time Comparison: Faster than 80% of sites

PageSpeed Insights

Avg. (All Categories) 69
Performance 51
Accessibility 95
Best Practices 73
SEO 91
Progressive Web App 36
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.up.com/index.htm
Updated: 25th April, 2021

2.32 seconds
First Contentful Paint (FCP)
29%
56%
15%

0.01 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
51

Performance

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

Metrics

Time to Interactive — 1.9 s
The time taken for the page to become fully interactive.
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).

Other

First CPU Idle — 1.9 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive up.com as laggy when the latency is higher than 0.05 seconds.
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://up.com/
http/1.1
0
149.99499998521
274
0
302
text/html
https://www.up.com/
http/1.1
150.6319999462
645.48299997114
313
0
302
text/html
http://www.up.com/up/index.htm
http/1.1
646.08600002248
829.57299996633
296
0
302
text/html
http://www.up.com/index.htm
http/1.1
830.09299996775
1023.1360000325
297
0
302
text/html
https://www.up.com/index.htm
http/1.1
1023.5569999786
1689.8679999867
6534
22768
200
text/html
Document
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
http/1.1
1702.7719999896
2180.0789999543
2581
12282
200
application/javascript
Script
https://www.up.com/cs/websites/up/sitenavigation.js
http/1.1
1702.9679999687
2165.779999923
39125
209696
200
application/javascript
Script
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
http/1.1
1703.1720000086
2154.7629999695
3641
14611
200
application/javascript
Script
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
http/1.1
1703.344999929
2194.538999931
6575
27372
200
application/javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
http/1.1
1703.4780000104
2451.0109999683
208096
1054937
200
text/css
Stylesheet
https://www.up.com/ssi/up/scripts/aos.js
http/1.1
1703.7240000209
2015.9229999408
14621
14244
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
http/1.1
1704.1650000028
2268.0369999725
89871
89493
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/js_rsp_link_modifier.js
http/1.1
1704.3940000003
2126.0110000148
1661
2617
200
application/javascript
Script
https://www.up.com/cs/groups/code/@system/documents/system/js_display_popup_graphic.js
http/1.1
1704.6509999782
2150.4590000259
1294
1691
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/build-site-nav.js
http/1.1
1704.8540000105
2194.3949999986
15066
14689
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
http/1.1
1704.9859999679
2083.9119999437
3331
2956
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
http/1.1
1705.2919999696
2206.6270000068
15495
65432
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/responsive-main.js
http/1.1
1705.4229999194
2103.6280000117
7094
6718
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
http/1.1
1705.6370000355
2196.6879999964
1024
650
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/slick.min.js
http/1.1
1705.7509999722
2028.583999956
43240
42863
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_ucm_home.css
http/1.1
1706.0079999501
2180.5989999557
1414
2925
200
text/css
Stylesheet
https://www.up.com/c02/showMessageForSuppliers.js
http/1.1
1706.194999977
2174.4379999582
342
0
302
text/html
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
http/1.1
2508.7269999785
3000.0109999673
19902
19495
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
http/1.1
2508.9409999782
3595.3120000195
277934
277414
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
http/1.1
2509.1069999617
3062.9059999483
362619
362100
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
http/1.1
2509.2339999974
2852.2779999766
86770
86252
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
http/1.1
2509.3300000299
3036.5339999553
1094453
1093934
200
image/png
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp_contact-us.svg
http/1.1
2509.4559999416
3387.1219999855
2020
1499
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-environment.svg
http/1.1
2509.8160000052
2688.1499999436
1448
929
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-ind-dev-real-est.svg
http/1.1
2510.2409999818
2770.7320000045
2704
2183
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-safety-signal.svg
http/1.1
2510.334999999
2777.5530000217
1725
1204
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
http/1.1
2510.4270000011
3070.4749999568
116029
115509
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
http/1.1
2510.6019999366
2942.3269999679
84908
84389
200
image/jpeg
Image
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_angelfish.js
http/1.1
2454.907999956
2744.3000000203
8087
19696
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/responsive-finish.js
http/1.1
2508.59699992
2764.9419999216
970
596
200
application/x-javascript
Script
https://c02.my.uprr.com/showMessageForSuppliers.js
http/1.1
2174.9500000151
2725.318999961
1105
1075
200
application/x-javascript
Script
data
2732.8059999272
2732.9619999509
0
8679
200
image/svg+xml
Image
data
2734.96599996
2735.011999961
0
282
200
image/svg+xml
Image
data
2737.3089999892
2737.3559999978
0
514
200
image/svg+xml
Image
data
2738.9800000237
2739.0489999671
0
3379
200
image/svg+xml
Image
data
2745.4709999729
2745.5690000206
0
4962
200
image/svg+xml
Image
data
2748.3990000328
2748.6459999345
0
17006
200
image/svg+xml
Image
https://www.up.com/fonts/oswald-light-webfont.woff
http/1.1
2752.4459999986
3206.2109999824
26595
26232
200
application/octet-stream
Font
https://www.up.com/fonts/Roboto-Regular.woff
http/1.1
2752.6279999875
3106.8909999449
77156
76792
200
application/octet-stream
Font
https://www.up.com/fonts/RobotoSlab-Bold.woff
http/1.1
2752.8579999926
3026.6490000067
92624
92260
200
application/octet-stream
Font
https://www.up.com/fonts/oswald-regular-webfont.woff
http/1.1
2753.1729999464
3055.4370000027
26435
26072
200
application/octet-stream
Font
https://www.up.com/fonts/Roboto-Bold.woff
http/1.1
2753.4079999896
3088.751000003
71856
71492
200
application/octet-stream
Font
https://www.up.com/fonts/oswald-bold-webfont.woff
http/1.1
2753.7449999945
3047.4430000177
27455
27092
200
application/octet-stream
Font
https://www.up.com/fonts/RobotoSlab-Regular.woff
http/1.1
2753.9010000182
3152.2460000124
91264
90900
200
application/octet-stream
Font
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_angelfish_agf.gif?t=pv&pv=%2Findex.htm&tt=Union+Pacific&vt=new&sc=direct&md=(none)&dp=24&sh=600&sw=800&bn=Chrome&bv=90&pn=Linux&pr=x86_64&bl=en-us&js=1.7&hn=www.up.com&vi=25840136&vs=258401361619343218&_=459337&v=037
http/1.1
2808.7789999554
3146.2090000277
557
43
200
image/gif
XHR
data
2879.2660000036
2879.3239999795
0
881
200
image/svg+xml
Image
data
2881.715000025
2881.7879999988
0
2561
200
image/svg+xml
Image
data
2884.0459999628
2884.0990000172
0
908
200
image/svg+xml
Image
data
2886.3129999954
2886.3689999562
0
1191
200
image/svg+xml
Image
data
2888.5249999585
2888.5809999192
0
1349
200
image/svg+xml
Image
https://www.up.com/cs/groups/code/@system/documents/webasset/ajax-loader.gif
http/1.1
2932.397000026
3060.1480000187
1204
1164
404
text/html
Image
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)
1719.487
6.575
1729.073
5.4
2208.283
32.704
2481.448
30.998
2512.538
24.151
2536.7
8.923
2756.786
63.704
2826.754
9.807
2836.586
10.314
2847.273
16.367
2867.863
6.337
2874.21
50.245
2928.814
90.707
3019.64
6.841
3034.905
51.997
3088.884
16.998
3119.232
19.122
3139.345
6.023
3145.973
17.22
3173.611
13.896
3196.244
5.671
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Up.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Up.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Up.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
15495
7693
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
6575
2804
Remove unused JavaScript — Potential savings of 37 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://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
37543
Enable text compression — Potential savings of 116 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89493
58542
https://www.up.com/ssi/up/scripts/slick.min.js
42863
32429
https://www.up.com/ssi/up/scripts/build-site-nav.js
14689
11895
https://www.up.com/ssi/up/scripts/aos.js
14244
9659
https://www.up.com/ssi/up/scripts/responsive-main.js
6718
4728
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
2956
1744
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
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 0 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://www.up.com/ssi/up/scripts/aos.js
171
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
0

Diagnostics

Avoids an excessive DOM size — 572 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
572
Maximum DOM Depth
16
Maximum Child Elements
11
Avoid chaining critical requests — 25 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Up.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.1 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://www.up.com/index.htm
272.1
6.272
1.318
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
177.085
126.535
1.501
Unattributable
74.66
0.986
0.123
Minimizes main-thread work — 0.6 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)
Other
169.962
Script Evaluation
169.745
Style & Layout
147.601
Rendering
65.93
Parse HTML & CSS
41.394
Script Parsing & Compilation
17.327
Garbage Collection
0.878
Keep request counts low and transfer sizes small — 45 requests • 2,869 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
45
2938005
Image
12
2051716
Font
7
413385
Script
17
254781
Stylesheet
2
209510
Document
1
6534
Other
6
2079
Media
0
0
Third-party
2
21007
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.50874977857382
0.25614383844746
0.0025234890160965
0.0017475382449601
0.00094396655794443
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 — 1 long task 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://www.up.com/index.htm
716
52
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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.

Opportunities

Remove unused CSS — Potential savings of 182 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Up.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208096
186148
Efficiently encode images — Potential savings of 226 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
221757
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
19495
9613
Avoid multiple page redirects — Potential savings of 600 ms
Redirects can cause additional delays before the page can begin loading. Up.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://up.com/
190
https://www.up.com/
230
http://www.up.com/up/index.htm
110
http://www.up.com/index.htm
70
https://www.up.com/index.htm
0

Diagnostics

Avoid enormous network payloads — Total size was 2,869 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1094453
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362619
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
277934
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208096
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
116029
https://www.up.com/fonts/RobotoSlab-Bold.woff
92624
https://www.up.com/fonts/RobotoSlab-Regular.woff
91264
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86770
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
84908

Metrics

First Contentful Paint — 1.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.5 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 4.3 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.775
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

First Meaningful Paint — 1.9 s
The time taken for the primary content of the page to be rendered.

Opportunities

Eliminate render-blocking resources — Potential savings of 1,360 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Up.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://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208096
750
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_ucm_home.css
1414
150
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
2581
150
https://www.up.com/cs/websites/up/sitenavigation.js
39125
350
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
3641
150
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
6575
150
https://www.up.com/ssi/up/scripts/aos.js
14621
150
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
470
https://www.up.com/cs/groups/code/@system/documents/webasset/js_rsp_link_modifier.js
1661
70
https://www.up.com/cs/groups/code/@system/documents/system/js_display_popup_graphic.js
1294
70
https://www.up.com/ssi/up/scripts/build-site-nav.js
15066
150
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
3331
70
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
15495
150
https://www.up.com/ssi/up/scripts/responsive-main.js
7094
70
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
1024
70
https://www.up.com/ssi/up/scripts/slick.min.js
43240
230
Properly size images — Potential savings of 1,306 KiB
Images can slow down the page's load time. Up.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1093934
788666
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
280439
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
277414
78377
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
115509
70955
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86252
66808
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
84389
51792
Serve images in next-gen formats — Potential savings of 1,323 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1093934
998016
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
299014
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86252
43640
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
19495
14335
Reduce initial server response time — Root document took 670 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.up.com/index.htm
667.308
Preload key requests — Potential savings of 1,520 ms
Key requests can be preloaded by using '<link rel=preload>'. Up.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.up.com/fonts/oswald-regular-webfont.woff
1520
https://www.up.com/fonts/RobotoSlab-Bold.woff
1490
https://www.up.com/fonts/Roboto-Regular.woff
1320
https://www.up.com/fonts/oswald-light-webfont.woff
1300
https://www.up.com/fonts/oswald-bold-webfont.woff
1080
https://www.up.com/fonts/RobotoSlab-Regular.woff
1020
https://www.up.com/fonts/Roboto-Bold.woff
1010

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Up.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.up.com/fonts/RobotoSlab-Bold.woff
0
92624
https://www.up.com/fonts/RobotoSlab-Regular.woff
0
91264
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
0
89871
https://www.up.com/fonts/Roboto-Regular.woff
0
77156
https://www.up.com/fonts/Roboto-Bold.woff
0
71856
https://www.up.com/ssi/up/scripts/slick.min.js
0
43240
https://www.up.com/cs/websites/up/sitenavigation.js
0
39125
https://www.up.com/fonts/oswald-bold-webfont.woff
0
27455
https://www.up.com/fonts/oswald-light-webfont.woff
0
26595
https://www.up.com/fonts/oswald-regular-webfont.woff
0
26435
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
0
19902
https://www.up.com/ssi/up/scripts/build-site-nav.js
0
15066
https://www.up.com/ssi/up/scripts/aos.js
0
14621
https://www.up.com/ssi/up/scripts/responsive-main.js
0
7094
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
0
6575
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
0
3641
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
0
3331
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
0
2581
https://c02.my.uprr.com/showMessageForSuppliers.js
0
1105
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
0
1024
https://www.up.com/ssi/up/scripts/responsive-finish.js
0
970
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.up.com/fonts/oswald-light-webfont.woff
453.76499998383
https://www.up.com/fonts/Roboto-Regular.woff
354.26299995743
https://www.up.com/fonts/RobotoSlab-Bold.woff
273.79100001417
https://www.up.com/fonts/oswald-regular-webfont.woff
302.26400005631
https://www.up.com/fonts/Roboto-Bold.woff
335.34300001338
https://www.up.com/fonts/oswald-bold-webfont.woff
293.69800002314
https://www.up.com/fonts/RobotoSlab-Regular.woff
398.34499999415
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
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 Failing Elements
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of up.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.
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.
`<object>` elements have `[alt]` 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.

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"]`
Up.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

Links do not 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.

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.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that up.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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.up.com/ssi/up/scripts/aos.js
https://www.up.com/ssi/up/scripts/aos.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 3 insecure requests 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://up.com/
Allowed
http://www.up.com/up/index.htm
Allowed
http://www.up.com/index.htm
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Registers an `unload` listener
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.
Source
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
TypeError: e.indexOf is not a function at S.fn.init.S.fn.load (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:84848) at HTMLDocument.<anonymous> (https://www.up.com/ssi/up/scripts/responsive-main.js:162:13) at e (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:30005) at t (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:30307)
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for up.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 up.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.
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.
Page isn’t 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.
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.

Content Best Practices

Links do not have descriptive text — 8 links found
Make use of descriptive link text to assist search engines in understanding the content.

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.
36

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 up.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) 68
Performance 38
Accessibility 97
Best Practices 73
SEO 92
Progressive Web App 42
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.up.com/index.htm
Updated: 25th April, 2021

2.63 seconds
First Contentful Paint (FCP)
14%
67%
19%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

Simulate loading on mobile
38

Performance

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

Metrics

Total Blocking Time — 160 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).
Cumulative Layout Shift — 0.035
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Estimated Input Latency — 20 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive up.com as laggy when the latency is higher than 0.05 seconds.
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://up.com/
http/1.1
0
157.28100000706
289
0
302
text/html
https://www.up.com/
http/1.1
157.78999999748
566.33200000215
313
0
302
text/html
http://www.up.com/up/index.htm
http/1.1
566.90200000594
665.49900000973
296
0
302
text/html
http://www.up.com/index.htm
http/1.1
665.98099999828
765.33200000995
297
0
302
text/html
https://www.up.com/index.htm
http/1.1
765.92700000037
1086.5350000095
6533
22768
200
text/html
Document
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
http/1.1
1098.8310000103
1512.0100000058
2596
12282
200
application/javascript
Script
https://www.up.com/cs/websites/up/sitenavigation.js
http/1.1
1099.1219999996
1610.2460000111
39117
209696
200
application/javascript
Script
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
http/1.1
1099.3220000091
1516.7310000106
3666
14611
200
application/javascript
Script
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
http/1.1
1099.5930000063
1565.5289999995
6575
27372
200
application/javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
http/1.1
1099.9620000075
1813.0349999992
208233
1054937
200
text/css
Stylesheet
https://www.up.com/ssi/up/scripts/aos.js
http/1.1
1100.283000007
1546.6260000103
14621
14244
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
http/1.1
1100.6670000061
1666.4030000102
89871
89493
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/js_rsp_link_modifier.js
http/1.1
1100.9380000032
1511.4270000049
1661
2617
200
application/javascript
Script
https://www.up.com/cs/groups/code/@system/documents/system/js_display_popup_graphic.js
http/1.1
1101.1460000009
1486.9600000093
1294
1691
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/build-site-nav.js
http/1.1
1101.3550000062
1557.1340000024
15066
14689
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
http/1.1
1101.4990000112
1356.7060000059
3331
2956
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
http/1.1
1101.634000006
1561.5740000067
15487
65432
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/responsive-main.js
http/1.1
1101.8230000045
1514.6210000094
7094
6718
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
http/1.1
1101.9170000072
1507.1529999987
1024
650
200
application/x-javascript
Script
https://www.up.com/ssi/up/scripts/slick.min.js
http/1.1
1102.1770000079
1603.3390000084
43240
42863
200
application/x-javascript
Script
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_ucm_home.css
http/1.1
1102.4150000012
1528.0029999994
1440
2925
200
text/css
Stylesheet
https://www.up.com/c02/showMessageForSuppliers.js
http/1.1
1102.6060000004
1501.6060000053
357
0
302
text/html
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
http/1.1
1871.2280000036
2502.2890000109
19902
19495
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
http/1.1
1871.4210000035
2292.0299999969
277933
277414
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
http/1.1
1871.7400000023
2321.1200000078
362619
362100
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
http/1.1
1871.9310000015
2292.3070000106
86771
86252
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
http/1.1
1872.0730000059
2528.2370000059
1094453
1093934
200
image/png
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp_contact-us.svg
http/1.1
1872.4300000031
2135.6340000057
2020
1499
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-environment.svg
http/1.1
1872.6910000114
2115.9400000033
1448
929
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-ind-dev-real-est.svg
http/1.1
1873.4620000032
2785.2010000061
2703
2183
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-safety-signal.svg
http/1.1
1873.6230000068
2302.5750000088
1724
1204
200
image/svg+xml
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
http/1.1
1874.0740000067
2260.4810000048
116029
115509
200
image/jpeg
Image
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
http/1.1
1874.2280000006
2238.4960000054
84908
84389
200
image/jpeg
Image
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_angelfish.js
http/1.1
1818.1210000039
2223.0200000049
8070
19696
200
application/javascript
Script
https://www.up.com/ssi/up/scripts/responsive-finish.js
http/1.1
1871.0410000058
2082.0430000022
970
596
200
application/x-javascript
Script
https://c02.my.uprr.com/showMessageForSuppliers.js
http/1.1
1501.9150000007
1907.699000003
1105
1075
200
application/x-javascript
Script
data
1928.0500000023
1928.1610000035
0
4185
200
image/svg+xml
Image
data
1930.3400000063
1930.4030000058
0
945
200
image/svg+xml
Image
data
1937.1499999979
1937.2450000083
0
4962
200
image/svg+xml
Image
data
1939.7650000028
1940.0030000106
0
17006
200
image/svg+xml
Image
https://www.up.com/fonts/oswald-light-webfont.woff
http/1.1
1943.2579999993
2823.5360000108
26595
26232
200
application/octet-stream
Font
https://www.up.com/fonts/Roboto-Regular.woff
http/1.1
1943.425999998
2431.0950000072
77156
76792
200
application/octet-stream
Font
https://www.up.com/fonts/RobotoSlab-Bold.woff
http/1.1
1943.6050000077
2431.3190000103
92624
92260
200
application/octet-stream
Font
https://www.up.com/fonts/oswald-regular-webfont.woff
http/1.1
1943.8340000052
2186.6880000016
26435
26072
200
application/octet-stream
Font
https://www.up.com/fonts/Roboto-Bold.woff
http/1.1
1944.1559999977
2277.5010000041
71856
71492
200
application/octet-stream
Font
https://www.up.com/fonts/oswald-bold-webfont.woff
http/1.1
1944.3620000093
2809.1459999996
27455
27092
200
application/octet-stream
Font
https://www.up.com/fonts/RobotoSlab-Regular.woff
http/1.1
1944.4820000062
2154.9519999971
91264
90900
200
application/octet-stream
Font
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_angelfish_agf.gif?t=pv&pv=%2Findex.htm&tt=Union+Pacific&vt=new&sc=direct&md=(none)&dp=24&sh=640&sw=360&bn=Chrome+Mobile&bv=90&pn=Android&pr=7&bl=en-us&js=1.7&hn=www.up.com&vi=53758872&vs=537588721619343241&_=518536&v=037
http/1.1
2235.2039999969
2505.9679999977
557
43
200
image/gif
XHR
data
2293.0380000034
2293.1000000099
0
881
200
image/svg+xml
Image
data
2295.5409999995
2295.6459999987
0
2561
200
image/svg+xml
Image
data
2297.8430000076
2297.8930000099
0
908
200
image/svg+xml
Image
data
2299.9540000019
2300.0060000049
0
1191
200
image/svg+xml
Image
data
2302.2639999981
2302.337000001
0
1349
200
image/svg+xml
Image
https://www.up.com/cs/groups/code/@system/documents/webasset/ajax-loader.gif
http/1.1
2352.1509999991
2609.3050000054
1203
1164
404
text/html
Image
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)
1116.058
6.588
1125.165
6.024
1648.211
35.211
1844.685
29.747
1874.537
25.293
1899.845
7.443
1951.903
46.616
2026.669
6.499
2201.875
7.063
2218.547
6.684
2251.448
27.726
2282.59
5.906
2288.511
50.194
2343.86
99.161
2443.048
6.124
2465.832
58.607
2538.988
9.787
2554.777
13.294
2568.963
13.618
2852.254
5.273
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images — Potential savings of 19 KiB
Time to Interactive can be slowed down by resources on the page. Up.com should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
19495
19495
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Up.com should consider minifying CSS files.
Minify JavaScript — Potential savings of 10 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Up.com should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
15487
7689
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
6575
2804
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 320 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.up.com/index.htm
321.605
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 0 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://www.up.com/ssi/up/scripts/aos.js
171
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
0

Diagnostics

Avoids an excessive DOM size — 572 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
572
Maximum DOM Depth
16
Maximum Child Elements
11
Avoid chaining critical requests — 25 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Up.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.7 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://www.up.com/index.htm
894.644
23.712
5.24
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
747.5
540.624
6.288
Unattributable
323.2
4
0.668
https://www.up.com/cs/websites/up/sitenavigation.js
123.904
86.624
22.54
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
118.988
0
0
Keep request counts low and transfer sizes small — 45 requests • 2,869 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
45
2938201
Image
12
2051713
Font
7
413385
Script
17
254788
Stylesheet
2
209673
Document
1
6533
Other
6
2109
Media
0
0
Third-party
2
21007
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.015161130884662
0.012070310581475
0.0018780253136201
0.001854817413518
0.001237792814047
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 — 8 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://www.up.com/index.htm
2232
234
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
13024
198
https://www.up.com/cs/websites/up/sitenavigation.js
5280
141
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
3780
119
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_angelfish.js
12810
111
https://www.up.com/ssi/up/scripts/aos.js
7680
101
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
12921
100
https://www.up.com/index.htm
2139
93
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

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

Max Potential First Input Delay — 200 ms
Users could experience a delay when interacting with the page.

Opportunities

Remove unused JavaScript — Potential savings of 37 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://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
37937
Enable text compression — Potential savings of 116 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89493
58542
https://www.up.com/ssi/up/scripts/slick.min.js
42863
32429
https://www.up.com/ssi/up/scripts/build-site-nav.js
14689
11895
https://www.up.com/ssi/up/scripts/aos.js
14244
9659
https://www.up.com/ssi/up/scripts/responsive-main.js
6718
4728
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
2956
1744

Diagnostics

Avoid enormous network payloads — Total size was 2,869 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1094453
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362619
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
277933
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208233
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
116029
https://www.up.com/fonts/RobotoSlab-Bold.woff
92624
https://www.up.com/fonts/RobotoSlab-Regular.woff
91264
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86771
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
84908
Minimize main-thread work — 2.3 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
721.816
Other
638.388
Style & Layout
509.748
Rendering
208.604
Parse HTML & CSS
163.208
Script Parsing & Compilation
74.052
Garbage Collection
18.896

Metrics

First Contentful Paint — 6.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 9.4 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 11.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 9.6 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 6.7 s
The time taken for the page's main thread to be quiet enough to handle input.
First Meaningful Paint — 6.7 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 13485 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 4,660 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Up.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://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208233
3480
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_ucm_home.css
1440
480
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
2596
480
https://www.up.com/cs/websites/up/sitenavigation.js
39117
1680
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
3666
480
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
6575
630
https://www.up.com/ssi/up/scripts/aos.js
14621
630
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
89871
2280
https://www.up.com/cs/groups/code/@system/documents/webasset/js_rsp_link_modifier.js
1661
180
https://www.up.com/cs/groups/code/@system/documents/system/js_display_popup_graphic.js
1294
180
https://www.up.com/ssi/up/scripts/build-site-nav.js
15066
630
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
3331
180
https://www.up.com/cs/groups/code/@system/documents/webasset/js_up_content_slider.js
15487
630
https://www.up.com/ssi/up/scripts/responsive-main.js
7094
330
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
1024
180
https://www.up.com/ssi/up/scripts/slick.min.js
43240
1080
Properly size images — Potential savings of 794 KiB
Images can slow down the page's load time. Up.com should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1093934
447485
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
189553
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_cvr_1-2021_lr.jpg
277414
48832
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_bar19_main_cover_mr.jpg
115509
47261
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86252
45014
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_hp_signal_maintainer_mr.jpg
84389
34578
Remove unused CSS — Potential savings of 191 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Up.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/code/@system/documents/webasset/css_up_styles-main-v2.css
208233
195099
Efficiently encode images — Potential savings of 226 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
221757
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
19495
9613
Serve images in next-gen formats — Potential savings of 1,323 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
1093934
998016
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
362100
299014
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
86252
43640
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
19495
14335
Avoid multiple page redirects — Potential savings of 1,920 ms
Redirects can cause additional delays before the page can begin loading. Up.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://up.com/
630
https://www.up.com/
780
http://www.up.com/up/index.htm
330
http://www.up.com/index.htm
180
https://www.up.com/index.htm
0
Preload key requests — Potential savings of 8,310 ms
Key requests can be preloaded by using '<link rel=preload>'. Up.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
URL Potential Savings (Ms)
https://www.up.com/fonts/oswald-regular-webfont.woff
8310
https://www.up.com/fonts/RobotoSlab-Bold.woff
7350
https://www.up.com/fonts/oswald-light-webfont.woff
7230
https://www.up.com/fonts/Roboto-Regular.woff
7230
https://www.up.com/fonts/oswald-bold-webfont.woff
6690
https://www.up.com/fonts/Roboto-Bold.woff
6360
https://www.up.com/fonts/RobotoSlab-Regular.woff
6330

Diagnostics

Serve static assets with an efficient cache policy — 21 resources found
Up.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.up.com/fonts/RobotoSlab-Bold.woff
0
92624
https://www.up.com/fonts/RobotoSlab-Regular.woff
0
91264
https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js
0
89871
https://www.up.com/fonts/Roboto-Regular.woff
0
77156
https://www.up.com/fonts/Roboto-Bold.woff
0
71856
https://www.up.com/ssi/up/scripts/slick.min.js
0
43240
https://www.up.com/cs/websites/up/sitenavigation.js
0
39117
https://www.up.com/fonts/oswald-bold-webfont.woff
0
27455
https://www.up.com/fonts/oswald-light-webfont.woff
0
26595
https://www.up.com/fonts/oswald-regular-webfont.woff
0
26435
https://www.uprr.com/graphics/uprr/responsive/global/print-logo.jpg
0
19902
https://www.up.com/ssi/up/scripts/build-site-nav.js
0
15066
https://www.up.com/ssi/up/scripts/aos.js
0
14621
https://www.up.com/ssi/up/scripts/responsive-main.js
0
7094
https://www.up.com/cs/resources/sitestudio/ssajax/ssajax.js
0
6575
https://www.up.com/cs/resources/wcm/sitestudio/wcm.toggle.js
0
3666
https://www.up.com/ssi/up/scripts/objectFitPolyfill.js
0
3331
https://www.up.com/cs/websites/up/sitenavigationfunctions.js
0
2596
https://c02.my.uprr.com/showMessageForSuppliers.js
0
1105
https://www.up.com/ssi/up/scripts/footer-reveal.min.js
0
1024
https://www.up.com/ssi/up/scripts/responsive-finish.js
0
970
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://www.up.com/fonts/oswald-light-webfont.woff
880.27800001146
https://www.up.com/fonts/Roboto-Regular.woff
487.66900000919
https://www.up.com/fonts/RobotoSlab-Bold.woff
487.7140000026
https://www.up.com/fonts/oswald-regular-webfont.woff
242.85399999644
https://www.up.com/fonts/Roboto-Bold.woff
333.34500000637
https://www.up.com/fonts/oswald-bold-webfont.woff
864.78399999032
https://www.up.com/fonts/RobotoSlab-Regular.woff
210.46999999089
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
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 Failing Elements
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_e_upo_englewood_mr.png
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk-brad-brown.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_instrk_embrace_diversty.jpg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-ind-dev-real-est.svg
img
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp_contact-us.svg
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-safety-signal.svg
img
https://www.up.com/cs/groups/public/@uprr/@corprel/documents/digitalmedia/img_up_ico_hp-environment.svg
img
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of up.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.
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 `[alt]` 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.

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"]`
Up.com may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Navigation

Heading elements are not 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.
Failing Elements

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.
73

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that up.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.

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

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.0
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.up.com/ssi/up/scripts/aos.js
https://www.up.com/ssi/up/scripts/aos.js.map
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 3 insecure requests 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://up.com/
Allowed
http://www.up.com/up/index.htm
Allowed
http://www.up.com/index.htm
Allowed
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Audits

Registers an `unload` listener
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.
Source
Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: the server responded with a status of 404 (Not Found)
TypeError: e.indexOf is not a function at S.fn.init.S.fn.load (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:84848) at HTMLDocument.<anonymous> (https://www.up.com/ssi/up/scripts/responsive-main.js:162:13) at e (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:30005) at t (https://www.up.com/ssi/up/scripts/jquery-3.5.0.min.js:2:30307)
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for up.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 up.com on mobile screens.
Document uses legible font sizes — 99.97% 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
.slick-dots li button
0.03%
0px
99.97%
≥ 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.
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.
Page isn’t 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.
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.

Content Best Practices

Links do not have descriptive text — 8 links found
Make use of descriptive link text to assist search engines in understanding the content.

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.
42

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 up.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.
Hosting

Server Location

Server IP Address: 69.58.254.142
Continent:
Country:
Region:
City:
Longitude:
Latitude:
Currencies:
Languages:

Web Hosting Provider

Name IP Address
Union Pacific Railroad Company
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Network Solutions, LLC 162.159.133.53
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: www.up.com
Issued By: Entrust Certification Authority - L1K
Valid From: 7th July, 2020
Valid To: 16th July, 2021
Subject: CN = www.up.com
O = Union Pacific Railroad Company
L = Omaha
S = US
Hash: 3b5f46f1
Issuer: CN = Entrust Certification Authority - L1K
OU = See www.entrust.net/legal-terms, (c) 2012 Entrust, Inc. - for authorized use only
O = Entrust, Inc.
S = US
Version: 2
Serial Number: 70172661283364093918261478383055929136
Serial Number (Hex): 34CAC351A0D13D869BBE5A74FF35FF30
Valid From: 7th July, 2024
Valid To: 16th July, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:82:A2:70:74:DD:BC:53:3F:CF:7B:D4:F7:CD:7F:A7:60:C6:0A:4C:BF
Extended Key Usage: TLS Web Server Authentication
CRL Distribution Points:
Full Name:
URI:http://crl.entrust.net/level1k.crl

Certificate Policies: Policy: 2.16.840.1.114028.10.1.5
CPS: https://www.entrust.net/rpa
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.entrust.net
CA Issuers - URI:http://aia.entrust.net/l1k-chain256.cer

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 55:81:D4:C2:16:90:36:01:4A:EA:0B:9B:57:3C:53:F0:
C0:E4:38:78:70:25:08:17:2F:A3:AA:1D:07:13:D3:0C
Timestamp : Jul 7 19:19:10.810 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:4D:E3:E2:A3:CB:C7:BA:D2:D6:BA:13:FA:
17:0F:1E:76:DA:47:D6:EF:71:83:30:4F:79:63:06:46:
17:9C:76:4F:02:20:5A:E1:98:52:B5:ED:E8:48:26:14:
C6:2C:96:8D:6A:2E:4F:01:CE:DC:BC:53:8F:D9:6F:EB:
7A:B6:B1:E2:08:33
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 56:14:06:9A:2F:D7:C2:EC:D3:F5:E1:BD:44:B2:3E:C7:
46:76:B9:BC:99:11:5C:C0:EF:94:98:55:D6:89:D0:DD
Timestamp : Jul 7 19:19:10.881 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D7:8C:19:F6:CF:B1:31:98:B8:53:34:
3E:59:3B:79:B6:17:A1:E6:6C:80:1C:14:1E:D6:51:CC:
41:60:B2:55:4F:02:20:11:E3:64:76:2D:34:08:8D:18:
5B:76:62:43:37:06:2C:1A:E9:43:05:C0:7F:A0:09:2A:
E5:97:EB:F0:03:48:AF
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Jul 7 19:19:10.864 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:FA:77:7F:C4:E6:F9:13:19:B5:B5:C8:
C4:68:09:A2:EE:F7:C4:C1:6F:80:6B:38:F5:54:21:D0:
AC:C0:32:CD:C5:02:21:00:CA:D3:A5:51:3D:F2:69:D3:
83:58:45:FD:17:02:52:A8:12:8C:08:5C:F7:D3:29:17:
E5:32:BA:49:F4:74:28:E1
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:up.com
DNS:www.up.com
Technical

DNS Lookup

A Records

Host IP Address Class TTL
up.com. 69.58.254.142 IN 1199

NS Records

Host Nameserver Class TTL
up.com. eth0.omsdp13d11.uprr.com. IN 7199
up.com. eth0.omhqp13d10.uprr.com. IN 7199

MX Records

Priority Host Server Class TTL
10 up.com. vx-cseg-01.omhq.uprr.com. IN 7199
10 up.com. vx-cseg-03.omsd.uprr.com. IN 7199

SOA Records

Domain Name Primary NS Responsible Email TTL
up.com. eth0.omsdp13d11.uprr.com. netengr.uprr.net. 7199

TXT Records

Host Value Class TTL
up.com. MS=81CAE9478966ED21B0B815969E00B91A3BDFD261 IN 3599
up.com. v=spf1 IN 3599
up.com. webexdomainverification.=63d51544-21b6-4d3f-b651-e6aa9d5058fe IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 25th April, 2021
Server: Apache
Cache-Control: no-cache, no-store
Expires: 22nd September, 2024
Content-Type: text/html; charset=utf-8
Pragma: no-cache
X-ORACLE-DMS-ECID: 5f3096a31acb85e1:-755023d8:178eefdb884:-8000-000000000114aa2b
X-Powered-By: Servlet/2.5 JSP/2.1
X-Frame-Options: SAMEORIGIN
Vary: Accept-Encoding
Set-Cookie: *
WEBSERVER_ID: hqp13e10

Whois Lookup

Created: 12th May, 1994
Changed: 23rd December, 2020
Expires: 13th May, 2022
Registrar: Network Solutions, LLC
Status: clientDeleteProhibited
clientTransferProhibited
serverDeleteProhibited
serverTransferProhibited
Nameservers: eth0.omhqp13d10.uprr.com
eth0.omsdp13d11.uprr.com
Owner Name: Union Pacific Railroad
Owner Organization: Union Pacific Railroad
Owner Street: 1400 DOUGLAS ST
Owner Post Code: 68179-0002
Owner City: OMAHA
Owner State: NE
Owner Country: US
Owner Phone: +1.4025444193
Owner Email: updnsacct@rbf.users.panix.com
Admin Name: ADMINISTRATOR, DOMAIN
Admin Organization: UNION PACIFIC RAILROAD
Admin Street: ATTN Brett Frankenberger - STOP 0650
Admin Post Code: 68179
Admin City: OMAHA
Admin State: NE
Admin Country: US
Admin Phone: +1.4025446091
Admin Email: updnsadmin@rbf.users.panix.com
Tech Name: Frankenberger, Brett
Tech Organization: Union Pacific Railroad
Tech Street: 1400 DOUGLAS ST STOP 0650
Tech Post Code: 68179-0650
Tech City: OMAHA
Tech State: NE
Tech Country: US
Tech Phone: +1.4025446091
Tech Email: rbf@panix.com
Full Whois: Domain Name: UP.COM
Registry Domain ID: 2636811_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.networksolutions.com
Registrar URL: http://networksolutions.com
Updated Date: 2020-12-23T17:27:19Z
Creation Date: 1994-05-12T04:00:00Z
Registrar Registration Expiration Date: 2022-05-13T04:00:00Z
Registrar: Network Solutions, LLC
Registrar IANA ID: 2
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registry Registrant ID:
Registrant Name: Union Pacific Railroad
Registrant Organization: Union Pacific Railroad
Registrant Street: 1400 DOUGLAS ST
Registrant City: OMAHA
Registrant State/Province: NE
Registrant Postal Code: 68179-0002
Registrant Country: US
Registrant Phone: +1.4025444193
Registrant Phone Ext:
Registrant Fax: +1.231231235
Registrant Fax Ext:
Registrant Email: updnsacct@rbf.users.panix.com
Registry Admin ID:
Admin Name: ADMINISTRATOR, DOMAIN
Admin Organization: UNION PACIFIC RAILROAD
Admin Street: ATTN Brett Frankenberger - STOP 0650
Admin City: OMAHA
Admin State/Province: NE
Admin Postal Code: 68179
Admin Country: US
Admin Phone: +1.4025446091
Admin Phone Ext:
Admin Fax: +1.4022332132
Admin Fax Ext:
Admin Email: updnsadmin@rbf.users.panix.com
Registry Tech ID:
Tech Name: Frankenberger, Brett
Tech Organization: Union Pacific Railroad
Tech Street: 1400 DOUGLAS ST STOP 0650
Tech City: OMAHA
Tech State/Province: NE
Tech Postal Code: 68179-0650
Tech Country: US
Tech Phone: +1.4025446091
Tech Phone Ext:
Tech Fax: +1.4022332132
Tech Fax Ext:
Tech Email: rbf@panix.com
Name Server: ETH0.OMSDP13D11.UPRR.COM
Name Server: ETH0.OMHQP13D10.UPRR.COM
DNSSEC: unsigned
Registrar Abuse Contact Email: abuse@web.com
Registrar Abuse Contact Phone: +1.8003337680
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2021-04-25T09:33:32Z <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


The data in Networksolutions.com's WHOIS database is provided to you by
Networksolutions.com for information purposes only, that is, to assist you in
obtaining information about or related to a domain name registration
record. Networksolutions.com makes this information available "as is," and
does not guarantee 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 of mass unsolicited, commercial
advertising or solicitations via direct mail, electronic mail, or by
telephone; or (2) enable high volume, automated, electronic processes
that apply to Networksolutions.com (or its systems). The compilation,
repackaging, dissemination or other use of this data is expressly
prohibited without the prior written consent of Networksolutions.com.
Networksolutions.com reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by these terms.

For more information on Whois status codes, please visit
https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en.

Nameservers

Name IP Address
eth0.omhqp13d10.uprr.com 45.54.254.90
eth0.omsdp13d11.uprr.com 173.229.253.153
Related

Subdomains

Similar Sites

Domain Valuation Snoop Score
$2,793,204 USD 4/5
$11,561 USD 2/5
$7,600 USD 2/5
0/5
$8,609 USD 2/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
$3,730 USD 3/5

Sites hosted on the same IP address