uptbox.com

uptbox.com may not be SSL secured

Free website and domain report on uptbox.com

Last Updated: 22nd June, 2022 Update Now
Overview

Snoop Summary for uptbox.com

This is a free and comprehensive report about uptbox.com. Uptbox.com is hosted in Australia on a server with an IP address of 103.224.182.250, where AUD is the local currency and the local language is English. Our records indicate that uptbox.com is owned/operated by GTOOP. If uptbox.com was to be sold it would possibly be worth $231 USD (based on the daily revenue potential of the website over a 24 month period). Uptbox.com is somewhat popular with an estimated 106 daily unique visitors. This report was last updated 22nd June, 2022.

About uptbox.com

Site Preview: uptbox.com uptbox.com
Title:
Description: See related links to what you are looking for.
Keywords and Tags: parked domain
Related Terms:
Fav Icon:
Age: Over 4 years old
Domain Created: 3rd February, 2020
Domain Updated: 17th June, 2022
Domain Expires: 3rd February, 2023
Review

Snoop Score

Valuation

$231 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,099,403
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 3
Moz Page Authority: 7

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 106
Monthly Visitors: 3,226
Yearly Visitors: 38,690
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $9 USD
Yearly Revenue: $110 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: uptbox.com 10
Domain Name: uptbox 6
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 74
Performance 100
Accessibility 59
Best Practices 77
SEO 100
Progressive Web App 35
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
100

Performance

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

Metrics

First Contentful Paint — 0.5 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.5 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.6 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 1.0 s
The time taken for the page to become fully interactive.
First CPU Idle — 1.0 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 90 ms
Users could experience a delay when interacting with the page.

Other

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 uptbox.com as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 20 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).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://uptbox.com/
0
98.503999877721
4447
4028
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
112.42499994114
131.43799989484
58537
165164
200
text/javascript
Script
http://uptbox.com/px.gif?ch=1&rn=8.435587897226323
113.63899987191
179.75399992429
275
42
200
image/gif
Image
http://uptbox.com/px.gif?ch=2&rn=8.435587897226323
113.78499981947
159.46400002576
275
42
200
image/gif
Image
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=800&rh=600&ww=1350&wh=940
216.29999997094
269.54200002365
10548
10204
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Open+Sans
273.70399981737
288.86099997908
1367
2434
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Quicksand
275.71800001897
291.32099985145
1327
1072
200
text/css
Stylesheet
http://ads.pro-market.net/ads/scripts/site-110930.js
279.73399986513
352.95500000939
1085
1404
200
application/x-javascript
Script
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
290.15899985097
373.81100002676
96086
95846
200
image/jpeg
Image
http://uptbox.com/public/legacy/10352/resources/arrows-bg-ext.png
290.39899981581
337.06399984658
1379
1143
200
image/png
Image
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300178&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608057033&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F
308.48699994385
397.02999987639
7185
9143
200
text/html
Document
https://fonts.gstatic.com/s/quicksand/v20/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wg.woff2
316.7929998599
320.61199983582
14383
13788
200
font/woff2
Font
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=vxk35x%20kxe;kw=vxk35x%20kxe;rnd=(1587608057110)
367.88999987766
411.89999994822
851
129
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
460.32599988393
477.32199984603
60239
165155
200
text/javascript
Script
https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans
516.62299991585
541.31400003098
0
0
-1
Stylesheet
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjgxLCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjEzNTAsImRoIjo5NDAsInJ3Ijo4MDAsInJoIjo2MDB9&t=1587608056&abp=0
537.12300001644
587.92699989863
356
0
200
text/plain
XHR
https://www.google.com/js/bg/r_kJ4x66L0q9ptqPN1EZdQZJVGt7LCWecB4z-4tOz0Y.js
558.85899998248
563.04799998179
6014
12318
200
text/javascript
Script
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)
130.511
7.52
175.885
12.949
300.33
39.409
344.626
5.614
383.489
11.738
430.281
8.232
438.68
40.432
479.645
8.403
520.792
42.932
571.575
12.889
593.862
87.157
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Uptbox.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Uptbox.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Uptbox.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Uptbox.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Uptbox.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Uptbox.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats — Potential savings of 53 KB
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 Size (Bytes) Potential Savings (Bytes)
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
95846
54366
Enable text compression — Potential savings of 8 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=800&rh=600&ww=1350&wh=940
10204
5908
http://uptbox.com/
4028
2208
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 100 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Uptbox.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Uptbox.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 258 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
96086
https://www.google.com/adsense/domains/caf.js
60239
http://www.google.com/adsense/domains/caf.js
58537
https://fonts.gstatic.com/s/quicksand/v20/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wg.woff2
14383
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=800&rh=600&ww=1350&wh=940
10548
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300178&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608057033&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F
7185
https://www.google.com/js/bg/r_kJ4x66L0q9ptqPN1EZdQZJVGt7LCWecB4z-4tOz0Y.js
6014
http://uptbox.com/
4447
http://uptbox.com/public/legacy/10352/resources/arrows-bg-ext.png
1379
https://fonts.googleapis.com/css?family=Open+Sans
1367
Avoids an excessive DOM size — 18 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
18
Maximum DOM Depth
7
Maximum Child Elements
7
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Uptbox.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.google.com/adsense/domains/caf.js
140.277
117.006
6.697
Other
134.379
9.35
3.106
Minimizes main-thread work — 0.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
178.478
Other
60.981
Rendering
48.539
Style & Layout
29.881
Script Parsing & Compilation
21.07
Parse HTML & CSS
5.634
Garbage Collection
5.178
Keep request counts low and transfer sizes small — 17 requests • 258 KB
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
17
264354
Script
5
136423
Image
4
98015
Font
1
14383
Document
3
12483
Stylesheet
3
2694
Other
1
356
Media
0
0
Third-party
11
151344
Minimize third-party usage — Third-party code blocked the main thread for 20 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
131975
22.816
1936
0

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.

Diagnostics

Serve static assets with an efficient cache policy — 5 resources found
Uptbox.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) Size (Bytes)
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
0
96086
http://uptbox.com/public/legacy/10352/resources/arrows-bg-ext.png
0
1379
http://uptbox.com/px.gif?ch=1&rn=8.435587897226323
0
275
http://uptbox.com/px.gif?ch=2&rn=8.435587897226323
0
275
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085

Diagnostics

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://fonts.gstatic.com/s/quicksand/v20/6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-wg.woff2
3.8189999759197
59

Accessibility

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

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Uptbox.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uptbox.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Uptbox.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
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>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
77

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.

Other

Does not use HTTPS — 9 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
http://uptbox.com/
http://www.google.com/adsense/domains/caf.js
http://uptbox.com/px.gif?ch=1&rn=8.435587897226323
http://uptbox.com/px.gif?ch=2&rn=8.435587897226323
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=800&rh=600&ww=1350&wh=940
http://ads.pro-market.net/ads/scripts/site-110930.js
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
http://uptbox.com/public/legacy/10352/resources/arrows-bg-ext.png
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjgxLCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjEzNTAsImRoIjo5NDAsInJ3Ijo4MDAsInJoIjo2MDB9&t=1587608056&abp=0
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 206
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.
URL Description
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300178&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608057033&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F#master-1
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=false&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300162%2C17300169%2C17300171%2C17300178&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608057033&u_w=800&u_h=600&biw=1350&bih=940&psw=1350&psh=932&frm=0&uio=ff6fa6st24sa11lt30sl1sr1-&cont=Sb&csize=w400h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F#master-1
Refused to apply style from 'https://fonts.googleapis.com/css?family=open%20sans%7Copen%20sans' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for uptbox.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 uptbox.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

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

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 uptbox.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 9 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
http://uptbox.com/
http://www.google.com/adsense/domains/caf.js
http://uptbox.com/px.gif?ch=1&rn=8.435587897226323
http://uptbox.com/px.gif?ch=2&rn=8.435587897226323
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=800&rh=600&ww=1350&wh=940
http://ads.pro-market.net/ads/scripts/site-110930.js
http://uptbox.com/public/legacy/10352/resources/arrows-bg.jpg
http://uptbox.com/public/legacy/10352/resources/arrows-bg-ext.png
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjgxLCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjEzNTAsImRoIjo5NDAsInJ3Ijo4MDAsInJoIjo2MDB9&t=1587608056&abp=0
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

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) 74
Performance 95
Accessibility 59
Best Practices 77
SEO 100
Progressive Web App 37
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
95

Performance

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

Metrics

First Contentful Paint — 1.8 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 1.8 s
The time taken for the primary content of the page to be rendered.
Speed Index — 2.1 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.6 s
The time taken for the page to become fully interactive.
First CPU Idle — 3.5 s
The time taken for the page's main thread to be quiet enough to handle input.

Other

Estimated Input Latency — 50 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 uptbox.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 Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://uptbox.com/
0
24.327999912202
4447
4028
200
text/html
Document
http://www.google.com/adsense/domains/caf.js
37.745000096038
56.00899993442
58538
165164
200
text/javascript
Script
http://uptbox.com/px.gif?ch=1&rn=7.862653666351034
39.687999989837
116.69100006111
275
42
200
image/gif
Image
http://uptbox.com/px.gif?ch=2&rn=7.862653666351034
39.857000112534
62.827999936417
275
42
200
image/gif
Image
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
140.80199995078
210.04400006495
9176
8832
200
text/javascript
Script
https://fonts.googleapis.com/css?family=Quicksand
214.29800009355
229.38999999315
1346
1089
200
text/css
Stylesheet
http://ads.pro-market.net/ads/scripts/site-110930.js
217.22800005227
315.39999996312
1085
1404
200
application/x-javascript
Script
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608064424&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=134&frm=0&uio=ff6fa6st24sa11lt48sl1sr1-&cont=Sb&csize=w412h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F
239.03300007805
324.27300000563
7394
9203
200
text/html
Document
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=vxk35x%20kxe;kw=vxk35x%20kxe;rnd=(1587608064528)
331.24199998565
373.02900012583
888
136
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
340.42000002228
359.86800002865
60301
165180
200
text/javascript
Script
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
413.31800003536
419.87799992785
795
260
200
image/png
Image
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjg0LCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjQxMiwiZGgiOjY2MCwicnciOjQxMiwicmgiOjY2MH0&t=1587608064&abp=0
427.97000007704
500.52400003187
356
0
200
text/plain
XHR
https://www.google.com/js/bg/r_kJ4x66L0q9ptqPN1EZdQZJVGt7LCWecB4z-4tOz0Y.js
448.68299993686
454.01700004004
6015
12318
200
text/javascript
Script
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)
49.243
7.566
90.309
8.558
233.632
30.858
339.495
12.331
353.397
7.503
396.425
44.693
441.139
6.558
454.323
12.283
478.124
120.659
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 3422 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
Resources, such as JavaScript and style sheets, can block the first paint of the page. Uptbox.com should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Uptbox.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Uptbox.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Uptbox.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Uptbox.com should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Uptbox.com should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression — Potential savings of 7 KB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Size (Bytes) Potential Savings (Bytes)
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
8832
4894
http://uptbox.com/
4028
2208
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 30 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Uptbox.com should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Uptbox.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 147 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.google.com/adsense/domains/caf.js
60301
http://www.google.com/adsense/domains/caf.js
58538
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
9176
https://www.google.com/dp/ads?max_radlink_len=60&r=m&cpp=0&client=dp-bodis31_3ph&channel=pid-bodis-gtest46%2Cpid-bodis-gcontrol102&hl=en&adsafe=low&type=3&kw=%20&terms=%20&swp=as-drid-2583416234859578&uiopt=true&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300162%2C17300169%2C17300171&format=r7&num=0&output=afd_ads&domain_name=uptbox.com&v=3&adext=as1%2Csr1&bsl=8&u_his=2&u_tz=-420&dt=1587608064424&u_w=412&u_h=660&biw=412&bih=660&psw=412&psh=134&frm=0&uio=ff6fa6st24sa11lt48sl1sr1-&cont=Sb&csize=w412h0&inames=master-1&jsv=13653&rurl=http%3A%2F%2Fuptbox.com%2F
7394
https://www.google.com/js/bg/r_kJ4x66L0q9ptqPN1EZdQZJVGt7LCWecB4z-4tOz0Y.js
6015
http://uptbox.com/
4447
https://fonts.googleapis.com/css?family=Quicksand
1346
http://ads.pro-market.net/ads/scripts/site-110930.js
1085
https://pbid.pro-market.net/engine?site=110930;size=1x1;e=0;category=vxk35x%20kxe;kw=vxk35x%20kxe;rnd=(1587608064528)
888
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
795
Uses efficient cache policy on static assets — 4 resources found
Uptbox.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) Size (Bytes)
http://uptbox.com/px.gif?ch=1&rn=7.862653666351034
0
275
http://uptbox.com/px.gif?ch=2&rn=7.862653666351034
0
275
https://afs.googleusercontent.com/dp-bodis/arrow-blue-2.png
82800000
795
http://ads.pro-market.net/ads/scripts/site-110930.js
86400000
1085
Avoids an excessive DOM size — 20 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
20
Maximum DOM Depth
6
Maximum Child Elements
7
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Uptbox.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.8 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.google.com/adsense/domains/caf.js
692.36
614.548
28.448
Other
285.992
34.532
10.756
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
122.648
85.1
4.096
Minimizes main-thread work — 1.2 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
821.848
Other
189.6
Script Parsing & Compilation
76.888
Style & Layout
68.044
Rendering
31.612
Garbage Collection
23.028
Parse HTML & CSS
17.684
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 147 KB
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
13
150891
Script
5
135115
Document
3
12729
Stylesheet
1
1346
Image
3
1345
Other
1
356
Media
0
0
Font
0
0
Third-party
9
136718

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.

Other

Total Blocking Time — 410 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).

Metrics

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

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 440 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
132248
439.768
1973
0
59

Accessibility

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

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Uptbox.com may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Uptbox.com may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Uptbox.com may provide relevant information that dialogue cannot, by using audio descriptions.

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.
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>` or `<template>` 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.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
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.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
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.

Internationalization and localization

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

Navigation

The page does not contain a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Failing Elements

Internationalization and localization

`<html>` element does not have 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.
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.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
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.
77

Best Practices

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

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
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.
Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
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.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
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 deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 7 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
http://uptbox.com/
http://www.google.com/adsense/domains/caf.js
http://uptbox.com/px.gif?ch=1&rn=7.862653666351034
http://uptbox.com/px.gif?ch=2&rn=7.862653666351034
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjg0LCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjQxMiwiZGgiOjY2MCwicnciOjQxMiwicmgiOjY2MH0&t=1587608064&abp=0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 130
Uses `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.
URL Location
https://www.google.com/adsense/domains/caf.js
line: 206
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for uptbox.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 uptbox.com on mobile screens.
Document uses legible font sizes — 93.67% 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
dynamic
.amo
6.33%
11px
Legible text
93.67%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
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.

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

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 uptbox.com. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

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

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 7 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
http://uptbox.com/
http://www.google.com/adsense/domains/caf.js
http://uptbox.com/px.gif?ch=1&rn=7.862653666351034
http://uptbox.com/px.gif?ch=2&rn=7.862653666351034
http://uptbox.com/glp?r=&u=http%3A%2F%2Fuptbox.com%2F&rw=412&rh=660&ww=412&wh=660
http://ads.pro-market.net/ads/scripts/site-110930.js
http://tracking.bodis.com/tlpv?d=eyJkb21haW5fbmFtZSI6InVwdGJveC5jb20iLCJzZXJ2ZXIiOjg0LCJ0ZXJtcyI6WyIxNzM5MDI4Il0sIlVSTCI6Imh0dHA6XC9cL3VwdGJveC5jb21cLyIsInJlZmVycmVyIjoiIiwiZHciOjQxMiwiZGgiOjY2MCwicnciOjQxMiwicmgiOjY2MH0&t=1587608064&abp=0
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.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 fallback content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
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.

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: 103.224.182.250
Continent: Oceania
Country: Australia
Australia Flag
Region:
City:
Longitude: 143.2104
Latitude: -33.494
Currencies: AUD
Languages: English

Web Hosting Provider

Name IP Address
Trellian Pty. Limited
Registration

Domain Registrant

Private Registration: No
Name: wei zhang
Organization: GTOOP
Country: CN
City: guangdong
State: guangzhohu
Post Code: 444112
Email: lkdder@outlook.com
Phone: +86.15211980418
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NameSilo, LLC 104.18.30.76
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
uptbox.com. 103.224.182.250 IN 3600

NS Records

Host Nameserver Class TTL
uptbox.com. ns1.above.com. IN 21600
uptbox.com. ns2.above.com. IN 21600

MX Records

Priority Host Server Class TTL
10 uptbox.com. park-mx.above.com. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
uptbox.com. ns1.above.com. hostmaster.trellian.com. 60

TXT Records

Host Value Class TTL
uptbox.com. 89bb1ae1b1f4297813f2fc6ff66f79edfb891ed6 IN 3600
uptbox.com. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: openresty
Date: 22nd June, 2022
Content-Type: text/html; charset=UTF-8
Cache-Control: post-check=0, pre-check=0
Expires: 1st January, 1970
Connection: keep-alive
Set-Cookie: *
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBANDrp2lz7AOmADaN8tA50LsWcjLFyQFcb/P2Txc58oYOeILb3vBw7J6f4pamkAQVSQuqYsKx3YzdUHCvbVZvFUsCAwEAAQ==_Kg/bX82AizNtCdaGyl5V6sn3z1vLVTF5p7sq5qRq1V2qTLHrz/x6luh2FYSZhfTCQGNaP2HOuPG4J3JoLJIx9A==
Pragma: no-cache

Whois Lookup

Created: 3rd February, 2020
Changed: 17th June, 2022
Expires: 3rd February, 2023
Registrar: NameSilo, LLC
Status: clientTransferProhibited
Nameservers: 2173.ns1.above.com
2173.ns2.above.com
Owner Name: Domain Administrator
Owner Organization: See PrivacyGuardian.org
Owner Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Owner Post Code: 85016
Owner City: Phoenix
Owner State: AZ
Owner Country: US
Owner Phone: +1.3478717726
Owner Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Admin Name: Domain Administrator
Admin Organization: See PrivacyGuardian.org
Admin Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Admin Post Code: 85016
Admin City: Phoenix
Admin State: AZ
Admin Country: US
Admin Phone: +1.3478717726
Admin Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Tech Name: Domain Administrator
Tech Organization: See PrivacyGuardian.org
Tech Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Tech Post Code: 85016
Tech City: Phoenix
Tech State: AZ
Tech Country: US
Tech Phone: +1.3478717726
Tech Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Full Whois: Domain Name: uptbox.com
Registry Domain ID: 2487890542_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namesilo.com
Registrar URL: https://www.namesilo.com/
Updated Date: 2022-06-17T07:00:00Z
Creation Date: 2020-02-03T07:00:00Z
Registrar Registration Expiration Date: 2023-02-03T07:00:00Z
Registrar: NameSilo, LLC
Registrar IANA ID: 1479
Registrar Abuse Contact Email: abuse@namesilo.com
Registrar Abuse Contact Phone: +1.4805240066
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: See PrivacyGuardian.org
Registrant Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Registrant City: Phoenix
Registrant State/Province: AZ
Registrant Postal Code: 85016
Registrant Country: US
Registrant Phone: +1.3478717726
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: See PrivacyGuardian.org
Admin Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Admin City: Phoenix
Admin State/Province: AZ
Admin Postal Code: 85016
Admin Country: US
Admin Phone: +1.3478717726
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: See PrivacyGuardian.org
Tech Street: 1928 E. Highland Ave. Ste F104 PMB# 255
Tech City: Phoenix
Tech State/Province: AZ
Tech Postal Code: 85016
Tech Country: US
Tech Phone: +1.3478717726
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: pw-2a6a2b58056eb9d94db88302844e2e34@privacyguardian.org
Name Server: 2173.ns1.above.com
Name Server: 2173.ns2.above.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2022-06-22T07:00:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS
database through the use of high-volume, automated, electronic processes. The
Data in our WHOIS database is provided for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. We do not guarantee its accuracy. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may
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 e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes that
apply to us (or our computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without our
prior written consent. We reserve the right to terminate your access to the
WHOIS database at our sole discretion, including without limitation, for
excessive querying of the WHOIS database or for failure to otherwise abide by
this policy. We reserve the right to modify these terms at any time.

Domains - cheap, easy, and secure at NameSilo.com

https://www.namesilo.com

Register your domain now at www.NameSilo.com - Domains. Cheap, Fast and Secure



Nameservers

Name IP Address
2173.ns1.above.com 103.224.212.5
2173.ns2.above.com 103.224.182.6
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$12,637 USD 2/5
$611 USD
$10 USD 1/5