9.4 sec in total
2.8 sec
5.6 sec
1 sec
Click here to check amazing Comingthru content for United States. Otherwise, check out these important facts you probably never knew about comingthru.com
A daily bicycling magazine with reviews, gear and commuting
Visit comingthru.comWe analyzed Comingthru.com page load time and found that the first response time was 2.8 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
comingthru.com performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value8.7 s
1/100
25%
Value10.1 s
9/100
10%
Value4,040 ms
1/100
30%
Value0.014
100/100
15%
Value10.7 s
22/100
10%
2752 ms
95 ms
136 ms
151 ms
163 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 55% of them (59 requests) were addressed to the original Comingthru.com, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Comingthru.com.
Page size can be reduced by 447.7 kB (34%)
1.3 MB
869.6 kB
In fact, the total size of Comingthru.com main page is 1.3 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. 55% of websites need less resources to load. Images take 723.9 kB which makes up the majority of the site volume.
Potential reduce by 66.0 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 66.0 kB or 83% of the original size.
Potential reduce by 19.9 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. Comingthru images are well optimized though.
Potential reduce by 246.2 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 246.2 kB or 66% of the original size.
Potential reduce by 115.6 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. Comingthru.com needs all CSS files to be minified and compressed as it can save up to 115.6 kB or 83% of the original size.
Number of requests can be reduced by 57 (56%)
102
45
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comingthru. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
comingthru.com
2752 ms
style.css
95 ms
slider.css
136 ms
instapress.css
151 ms
jquery.fancybox.css
163 ms
style.css
165 ms
jetpack.css
156 ms
jquery.js
248 ms
jquery-migrate.min.js
211 ms
jquery.fancybox-1.3.4.pack.js
231 ms
scripts.js
226 ms
woo_tabs.js
226 ms
superfish.js
228 ms
cufon-yui.js
280 ms
Nevis.font.js
298 ms
wooslider.js
297 ms
buttons.js
11 ms
star-rating.css
311 ms
boxed-red.css
310 ms
shortcodes.css
319 ms
custom.css
344 ms
comingthru.com
1462 ms
instapress.js
365 ms
devicepx-jetpack.js
6 ms
gprofiles.js
59 ms
wpgroho.js
373 ms
e-201611.js
7 ms
comingthru.json
46 ms
blogger.js
107 ms
search_box_bg.jpg
203 ms
search_button_bg.png
200 ms
ct_logo_500px-300x188.png
202 ms
thumb.php
249 ms
thumb.php
248 ms
thumb.php
248 ms
thumb.php
248 ms
thumb.php
247 ms
thumb.php
326 ms
thumb.php
460 ms
thumb.php
459 ms
thumb.php
455 ms
thumb.php
408 ms
thumb.php
392 ms
thumb.php
435 ms
thumb.php
555 ms
thumb.php
578 ms
thumb.php
538 ms
thumb.php
558 ms
thumb.php
562 ms
thumb.php
563 ms
thumb.php
641 ms
thumb.php
659 ms
thumb.php
667 ms
thumb.php
668 ms
manifesto.png
631 ms
comingthru_logo_transparent_square_small.png
649 ms
woothemes.png
701 ms
app.js
402 ms
nav_bg.jpg
695 ms
dot.gif
703 ms
fleche1.png
711 ms
fleche2.png
716 ms
ico-arrow.png
723 ms
more-entries.jpg
754 ms
widget_li_bg.jpg
734 ms
widget_link_bg.jpg
742 ms
count.js
186 ms
ga.js
137 ms
g.gif
133 ms
hovercard.css
127 ms
services.css
139 ms
getAllAppDefault.esi
130 ms
likebox.php
255 ms
__utm.gif
17 ms
count-data.js
73 ms
count-data.js
117 ms
getSegment.php
18 ms
checkOAuth.esi
26 ms
t.dhj
14 ms
t.dhj
17 ms
cm
60 ms
x35248
151 ms
s-3271.xgi
20 ms
hDvwL1_H7g-.css
190 ms
56WNbrUYLbL.css
235 ms
q68gy-v_YMF.js
318 ms
FJmpeSpHpjS.js
385 ms
0wM5s1Khldu.js
313 ms
1bNoFZUdlYZ.js
310 ms
hbpix
42 ms
pixel
45 ms
16 ms
13 ms
xrefid.xgi
17 ms
pixel
17 ms
2981
34 ms
419112_403594969654427_1252148877_n.jpg
248 ms
564358_422560104424580_360340447_n.jpg
285 ms
1927663_975104765913213_9107484668722696801_n.jpg
325 ms
11960231_10154123691388356_4464110552748288433_n.jpg
369 ms
11937441_966751943373510_5889561012373106322_n.jpg
369 ms
66894_10207633469812371_7234407922480692837_n.jpg
364 ms
11987207_964141370296193_8185433282734050804_n.jpg
397 ms
wL6VQj7Ab77.png
50 ms
s7jcwEQH7Sx.png
49 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
82 ms
comingthru.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
comingthru.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
comingthru.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comingthru.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Comingthru.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
comingthru.com
Open Graph data is detected on the main page of Comingthru. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: