6.3 sec in total
2.4 sec
3.7 sec
172 ms
Click here to check amazing TRAFFIC content. Otherwise, check out these important facts you probably never knew about traffic.ly
Visit traffic.lyWe analyzed Traffic.ly page load time and found that the first response time was 2.4 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
traffic.ly performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value4.8 s
31/100
25%
Value2.9 s
95/100
10%
Value110 ms
97/100
30%
Value0
100/100
15%
Value4.1 s
86/100
10%
2406 ms
31 ms
75 ms
102 ms
129 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 59% of them (38 requests) were addressed to the original Traffic.ly, 17% (11 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Traffic.ly.
Page size can be reduced by 1.2 MB (15%)
8.1 MB
6.9 MB
In fact, the total size of Traffic.ly main page is 8.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 59.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 12.6 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 59.8 kB or 81% of the original size.
Potential reduce by 202.6 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. TRAFFIC images are well optimized though.
Potential reduce by 542.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 542.7 kB or 70% of the original size.
Potential reduce by 387.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Traffic.ly needs all CSS files to be minified and compressed as it can save up to 387.1 kB or 84% of the original size.
Number of requests can be reduced by 32 (63%)
51
19
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TRAFFIC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
traffic.ly
2406 ms
css
31 ms
woocommerce-layout.css
75 ms
woocommerce.css
102 ms
style.css
129 ms
font-awesome.css
273 ms
ionicons.min.css
119 ms
jquery.js
124 ms
jquery-migrate.min.js
50 ms
wp-emoji-release.min.js
66 ms
add-to-cart.min.js
49 ms
jquery.blockUI.min.js
54 ms
woocommerce.min.js
51 ms
jquery.cookie.min.js
56 ms
cart-fragments.min.js
58 ms
skip-link-focus-fix.js
58 ms
flowtype.js
75 ms
jquery.fitvids.js
81 ms
fastclick.js
84 ms
ekko-lightbox.js
82 ms
plugins.js
131 ms
slides.js
86 ms
scripts.js
98 ms
bootstrap.min.js
128 ms
wp-embed.min.js
106 ms
woocommerce-smallscreen.css
26 ms
ga.js
455 ms
video-icon.svg
449 ms
xQWRC9Enat4
452 ms
video-4.jpg
484 ms
img-16.jpg
422 ms
img-47.jpg
420 ms
img-69.jpg
425 ms
ipad-33.png
422 ms
ipad-32.png
483 ms
ipad-31.png
485 ms
img-33.jpg
422 ms
img-54.jpg
485 ms
img-68.jpg
483 ms
67-01.jpg
483 ms
67-02.jpg
486 ms
67-03.jpg
485 ms
img-67.jpg
683 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
362 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
361 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
365 ms
2NBgzUtEeyB-Xtpr9bm1Cczai8e7xzqnKiVb1EwOy0E.ttf
366 ms
UC3ZEjagJi85gF9qFaBgIETamuWRjOQSPxoOXgdYd7c.ttf
366 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
364 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
365 ms
toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf
364 ms
toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf
365 ms
share.js
484 ms
hotjar-126216.js
348 ms
www-embed-player-vflRGs1ko.css
125 ms
www-embed-player.js
223 ms
base.js
339 ms
__utm.gif
119 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
150 ms
collect
172 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
79 ms
ad_status.js
62 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
91 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
91 ms
traffic.ly accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
traffic.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
traffic.ly SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Traffic.ly can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Traffic.ly main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
traffic.ly
Open Graph description is not detected on the main page of TRAFFIC. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: