2.4 sec in total
448 ms
1.6 sec
353 ms
Visit fogeek.com now to see the best up-to-date Fogeek content and also check out these interesting facts you probably never knew about fogeek.com
fogeek online wholesale store features 100,000+ cell phone accessories for iPhone, Samsung and more at lowest prices from China.
Visit fogeek.comWe analyzed Fogeek.com page load time and found that the first response time was 448 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
fogeek.com performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value7.2 s
5/100
25%
Value7.8 s
23/100
10%
Value1,370 ms
16/100
30%
Value0.104
89/100
15%
Value8.9 s
34/100
10%
448 ms
528 ms
257 ms
139 ms
144 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 60% of them (24 requests) were addressed to the original Fogeek.com, 33% (13 requests) were made to Img.fogeek.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (894 ms) relates to the external source Api.wisdomseller.com.
Page size can be reduced by 281.6 kB (14%)
2.0 MB
1.7 MB
In fact, the total size of Fogeek.com main page is 2.0 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. 30% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 95.5 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 95.5 kB or 88% of the original size.
Potential reduce by 74.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. Fogeek images are well optimized though.
Potential reduce by 104.0 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 104.0 kB or 61% of the original size.
Potential reduce by 7.2 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. Fogeek.com needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 37% of the original size.
Number of requests can be reduced by 5 (14%)
37
32
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fogeek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
fogeek.com
448 ms
jquery-1.8.2.js
528 ms
home_all.css
257 ms
home_all.js
139 ms
bar.js
144 ms
slide.js
141 ms
imglazyload.js
190 ms
client.jsp
894 ms
d077fefa-56ba-4989-a5d9-0535cd61a059.jpg
503 ms
iPhone.jpg
375 ms
iPad.jpg
369 ms
iPod.jpg
373 ms
samsung.jpg
373 ms
tablet.jpg
372 ms
sony.jpg
391 ms
lg.jpg
519 ms
42854879-b2ac-48be-9773-d5e082cd3f76.jpg
429 ms
51c9487b-57be-4fb9-9449-dd944e30bcf4.jpg
620 ms
53a6e3e5-dcb0-4e63-b240-9a51cf2f8a26.jpg
575 ms
0acbd204-93c1-49da-a743-675a213380f8.jpg
453 ms
d67e01c0-db4d-448c-85b2-c0fa9545d0e1.jpg
374 ms
a0951c36-c8e4-4ce5-b761-7c3fca79cc0d.jpg
438 ms
5ab6f380-d22e-44af-b689-e9f4490a78d7.jpg
552 ms
df37c1fc-466b-4df8-9b62-3e59a77526a4.jpg
501 ms
9eb13653-4030-4eb8-bc7e-22f7006fa520.jpg
515 ms
e7ef893f-644d-4f12-9044-74cf007804c8.jpg
535 ms
1a3705b2-1962-40ab-999b-aa3e9f929d11.jpg
563 ms
20200418142733_1441.jpg
580 ms
buy-loader.gif
73 ms
webImg.png
577 ms
msn.jpg
74 ms
skype.jpg
199 ms
logo.jpg
127 ms
all_bg.gif
135 ms
lazylogo.png
137 ms
bottom_title_bg.jpg
137 ms
analytics.js
6 ms
collect
38 ms
ajax.aspx
165 ms
ajax.aspx
97 ms
fogeek.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
fogeek.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
Page has valid source maps
fogeek.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fogeek.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fogeek.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.
fogeek.com
Open Graph description is not detected on the main page of Fogeek. 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: